Oh thank God. There aren't nearly enough ways to write javascript.
There's no Javascript (or any other runtime) code in this at all. It all happens at compile-time.
But you probably are going to be running this as JS eventually
HypeScript: Simplified TypeScript type system in TypeScript's own type system
21–30 of 84 posts
Re: HypeScript: Simplified TypeScript type system in TypeScript's own type system
#22“I'm not about to start using it for real projects, it's really just a thought experiment about how nice JavaScript could be with an alternative syntax.” - jashkenas 2009 https://news.ycombinator.com/item?id=1014225
Man, I know this wasn't really the intention of the comment, but I just read through that thread and got a little nostalgic. Crazy that was like 13 years ago. Sheesh.
Re: HypeScript: Simplified TypeScript type system in TypeScript's own type system
#23This guy's like, "I see your Lisp in Lisp and raise you..."
Re: HypeScript: Simplified TypeScript type system in TypeScript's own type system
#24Re: HypeScript: Simplified TypeScript type system in TypeScript's own type system
#25Please tell me this means you can do dependent types! I have no idea how this works, seems like magic and seems like anything is possible.
Maybe "dependent-but-stringly typed" is possible?
Re: HypeScript: Simplified TypeScript type system in TypeScript's own type system
#26Can we read the source file from filesystem, then pass into type checker like this ?
Re: HypeScript: Simplified TypeScript type system in TypeScript's own type system
#27Re: HypeScript: Simplified TypeScript type system in TypeScript's own type system
#28Am I the only one that feels uncomfortable with all that usage of strings in TS’s type system? Why not use pure literals instead of string literals? This is a genuine question, I’m trying to find out what the pros and cons where in the decision making process.
As others have pointed out, they're not really "strings" per se, or at least can be a lot stricter than a string might seem when used right. We use that constantly for useful things.
The bigger reason why it is this way is to ensure you can write type annotations for stringly-typed Javascript. While Typescript is it's own thing really at this point, it still is very focused on making it possible to type-annotate JS code.
type Event = 'onClick' | 'onHover'
// some stringly typed javascript can now be nicely typed
something.triggerEvent('onClick', someData)
Re: HypeScript: Simplified TypeScript type system in TypeScript's own type system
#29This is insanely cool voodoo. But... I may be lacking in imagination here... I'm trying to think of how I'd actually use it. Maybe it'll come to me in the middle of the night 8)
I do really wish TS had actual inbuilt reflective type checking along the lines of this: https://github.com/Hookyns/tst-reflect ...I can hazily see some kind of monstrosity that could come from linking these things together hah