Eli
For clarity for whoever implements this (as there isn't a linked a Zulip thread), this wouldn't be for type annotations, where the existing type hole (`_`) type would be used...
Instead of using `type`, what about integrating with [standard-schema](https://github.com/standard-schema/standard-schema)? That'd let you use zod, valibot, etc, parsers without a) pulling them in, b) picking a specific one, but allows users...
See also: #233
~Blocked on #229
I'd guess that slow types will remain. For large projects, even a 10× speedup might not be enough, and the issue of [types becoming unstable over time](https://jsr.io/docs/about-slow-types#:~:text=tsc%20does%20not%20produce%20stable%20type%20information%20over%20time) will remain (although...
> [@lishaduck](https://github.com/lishaduck) Feel free to raise a PR. I'd love too, but I've currently frozen my backlog to ensure I actually fill out my college apps (and I'm currently using...
May I ask a better way? `Future.wait` loses type safety.
> [@lishaduck](https://github.com/lishaduck) This works in dart That's a thing!? I never knew that. Thanks!
See #505 for a previous proposal (with a linked PR)
> It's different. This feature request is more generic, while the issue you linked seems only focus on installation. That issue started out as installation, but is now a generic...