Neil Girdhar

@marvingreenberg seems like your solution doesn't currently work?

Thanks for posting this. I suggest posting this to the discuss, which should attract more attention.

FYI discuss is here: https://discuss.python.org/

@ippeiukai I believe Eric brought up your issue [here](https://discuss.python.org/t/compatibility-of-protocol-class-object-with-type-t-and-type-any/48442/4) in case you wanted to participate!

Thank you for the fast reply! I intend to compare your results with a custom implementation on the same data. That means I need to get it working in modern...

Yeah, that's what I figured. I tried to illustrate some reasonable uses of strings. I'm not sure how you feel about the "variable docstring", which some editors recognize. As far...

Please don't use the same documentation as PLW0105: strings are not reasonable documentation in Python, and I don't think the linter should suggest that.

Maybe Ruff should flag "attribute docstrings" using a separate rule to convert them to annotated annotations? ```python x: int "blah" ``` becomes ```python x: Annotated[int, "blah"] ``` This is more...

The refactor's elimination of the list is a significant improvement. The ordering preserved by the interface for intersection is also an improvement. FYI, You can make `intersection` a lot faster...

@twiddli pretty sure he can't support it since dicts don't have efficient indexing.