of course it works but only because I realized last week that the Unicode 17 update broke us
protip: do not take a dependency on Unicode for your language or type system
Yay "JS identifiers are defined in terms of Unicode classes" and "TS has Uppercase/Lowercase transformation types"
brb compiling TS RC with Go RC
@jorropo.net burst my bubble; this could actually be observable by a very goofy case of a boxed nil interface call, something that the Go test suite did not test!
But, it's still salvageable; just generate one wrapper instead of zero, which is just a simplification of my second CL. redone
But it does change stack traces, but thankfully just for that edge case, which, again did not have a test ðŸ«
That or, maybe the spec should change or be reinterpreted in such a way that we can avoid the wrappers entirely...?
WELCOME TO WASHINGTON, SOCCER FANS. Get acquainted with our state via this highly accurate and mostly-to-scale map.
📣 TypeScript 7's Release Candidate is now out! 📣
The new native rewrite is almost here. Try it out on your codebases, and make sure your team is ready for the upcoming 7.0 release!