DetachHead

hmm, thinking about this more maybe it doesnt make sense to support it. i cant think of a situation where it'd be correct ```py def foo(value: object) -> value is...

this is more of an issue in basedmypy than upstream, since variables are narrowed on initial assignment so it's easier to run into ```py a: int | None = None...

could this be fixed by updating the `__eq__` from `object` to only allow `Self`: ```py def __eq__(self, __value: Self) -> bool: ... ``` because currently since it takes `object` no...

Yeah but it should be enabled by default

nah, because not only does it not work at all, it also won't allow for conditionally defining stuff depending on whether you're using basedmypy or mypy, like in my example

going to rename #109 instead of using this separate issue

yea i think it should be enabled. btw whats the signature of `dict.update` look like? i assumed it would be covered by the existing rules unless some special case shit...

i think this would be good if it still allowed you to use based features in "private" code (ie. anything starting with `_`)

thanks for the reply. this schema was generated by pydantic so i raised it there and will see what they say https://github.com/pydantic/pydantic/issues/5316

got it to work with `https://gitpkg.vercel.app/api/pkg?url=DetachHead/svelte-material-ui/packages/accordion&commit=7406097673b76eefe989a89dccd3584e99c3e41c&scripts.postinstall=npm%20install%20--ignore-scripts%26%26%20npm%20run%20build` but yeah it would be nice if it did this automatically without having to manually specify scripts that usually get automatically run anyway