Spec for subtypes of type variable constraints too vague
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 文件
- 描述清晰度
- 需要釐清
- 活躍度
- 停滯
- 技術堆疊
- python
研究方向
從 docs/spec/generics.rst 開始,尤其是其中連結的關於受約束型別變數的章節,並檢視涉及 C[bool]、建構函式推論和逆變位置的範例。在確定預期語意之前,閱讀四條提議的規則以及現有的留言討論。達成共識並更新規格以清楚說明行為,即表示完成。
由索引模型根據 Issue 內容生成。
描述
The spec is very vague when it comes to instantiating a type variable with constraints with a subtype of one of the constraints:
Let's look at a slightly more involved example:
class C[T: (int, str)]:
def __init__(self, t: T) -> None:
self.t: T = t
c = C(True)
The example in the spec implies that the constructor call is fine because True is of type bool, which is a subtype of int, and T can be instantiated to int. Thus, c should have type C[int]. This makes perfect sense and is totally natural if you write a bidirectional type checker anyway. Nothing controversial here.
What about the following?
c: C[bool] = ...
Does the type "widening" to the base type mentioned in the spec apply here too and this has to be interpreted as if the user had written C[int]? At least pyright interprets it this way. I'm wondering if this was the intent of the spec? Off the top of my head, I cannot think of a situation where this would be a useful feature (but I'm happy to convinced otherwise). Moreover, this can become rather counter-intuitive when C[bool] appears in contravariant positions.
I would like to get a conversation going that crystallizes the intent of the spec in this regard. If we come to a conclusion, I'd be more than happy to update the docs to reflect this outcome.
Here's how I would roughly specify the feature:
-
Explicit instantiations of constrained type variables via class/alias specializations must be taken at face value and not automatically be widened to base types. If the explicitly mentioned type argument is neither a type variable nor a type equivalent to one of the constraints, that's a type error. For the exact meaning of "equivalent", I would suggest to pick an equivalence relation on the more syntactic side of the spectrum of possibilities but haven't thought about this aspect too deeply so far.
-
Explicitly instantiating a constrained type variable
Twith another type variableSis only allowed ifSalso has constraints and each of them is also listed inT's constraints (up to the same equivalence as above). (I avoided the word "subset" on purpose since that's too easy to interpret as "subtype", which I do not mean!) -
All of this this should also apply to generic functions should there ever be a way to explicitly specialize them.
-
When inferring type arguments for generic function calls, including constructor calls, the function is conceptually "exploded" into an overloaded function with one case for each constraint and overload resolution decides which constraint to pick as the instantiation for the type variable.
This gets particularly gnarly in the presence of multiple matching constraints caused by multiple inheritance. Being consistent with overload resolution seems like a good property to have here.
This covers the covariant case illustrated in the example above where
boolgets "widened" toint. It also covers the contravariant case, where the functiondef higher_order[T: (int, str)](f: Callback[[T], None]): ...can be called with an argument of type
Callback[[float], None]andTgets instantiated toint. (In some sense,floatgets "narrowed" tointhere.)
- 主要語言
- Python
- 星號
- 1.8k
- 分支
- 302
- 平均合併
- 4 小時 16 分鐘
- 30 天內合併 PR
- 7
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
python/typing 的其他 Issue
-
topic: typing spec
難度 2/5 1-3 小時 新手友好度 72/100
python/typing#2356 · 2 則留言 · 1 個 reaction ·
維護者通常 1 天內回覆
-
topic: typing spec
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
Update reference/generics.html with PEP695 type parameter syntax可能已有人在做 @BHUVANSH855 於 180 天前認領。 未關閉topic: documentation
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 1 天內回覆
-
topic: documentation
難度 2/5 1-3 小時 新手友好度 65/100
python/typing#2150 · 2 則留言 · 2 個 reaction ·
維護者通常 1 天內回覆
-
Finals and Literals: Spec contradiction可能已有人在做 @srittau 於 34 天前認領。 未關閉topic: conformance tests topic: typing spec
難度 3/5 1-2 天 新手友好度 72/100
維護者通常 1 天內回覆
相似的 Issue
-
enhancement P2
難度 2/5 1-3 小時 新手友好度 78/100
Toloka/tolokaforge#1776 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 88/100
TencentCloud/Octop#1622 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 68/100
-
Rust: `const _` gets its file's node ID, so the file node is relabelled `_` and gains a self-loop未關閉
難度 2/5 1-3 小時 新手友好度 78/100
Graphify-Labs/graphify#4064 · 1 則留言 ·
維護者通常 2 天內回覆