Declaring classes as pure mixins
還沒有人認領這個 Issue。
- 主要語言
- Python
- 星號
- 1.8k
- 分支
- 302
- 平均合併
- 23 小時
- 30 天內合併 PR
- 8
描述
(This is an extension to #241 and copied from the discussion there.)
What about having a magic class decorator (with no or minimal runtime effect) or a base class that declares a class as a "pure mixin"? A pure mixin could only be used for implementation inheritance, and it wouldn't be type checked by itself at all -- it would only be type checked as part of implementation inheritance. I think that this would allow type checkers to check some mixin use cases that are tricky right now with minimal code changes. The alternative would be to use ABCs to declare the things that the mixin expects to be defined elsewhere, but they are harder to use and arguably add boilerplate.
Example:
@puremixin
class MyMixin:
def do_stuff(self) -> int:
self.one_thing() # ok, even though not defined in this class
return self.second_thing(1) # also ok
class Thing(Implementation[MyMixin]):
def one_thing(self) -> None: pass # ok
def second_thing(self, x: int) -> str: # error: return type not compatible with do_stuff
return 'x'
貢獻指南
這個儲存庫沒有索引到貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
這是從 #241 的討論中複製的設計提案,沒有指定任何檔案或測試。先閱讀 #241 及其討論,然後釐清 pure-mixin 裝飾器或基底類別的語意,以及應如何檢查所示的 Implementation[MyMixin] 情況;達成共識的設計後才算完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- tooling
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 25/100