DetachHead
DetachHead
related: #576 if we do that, then id rather the inlay hints match that syntax
i'm going to put all non-standard features behind an `allowNonStandardFeatures` option i think, that way users can decide for themselves
we need to also account for their usage inside generics, because these two mean the same thing at runtime: ```py foo: list[(int, str)] bar: list[int, str] ``` the only way...
i dont think this is feasible unless we can come up with a solution to both of those problems
i don't like the idea of changing the syntax to something that means something else in certain contexts, and is only sometimes allowed. this will just add more confusion to...
it should be configurable so it depends on #539, and when running in "application" mode (ie. not a library), it should also report unused public functions as well as not...
depends on #539
i already raised #21 for `assert_type` but i like the idea of making it configurable
interesting idea. personally i never use `__all__` and instead just rely on prefixing symbols with `_` to mark them as private i think both ways are pretty gross, i wish...
some thoughts i've had about this feature: - having everything be public by default and using a `@private` decorator to change that will allow this feature to work for library...