←back to thread

511 points mootrichard | 2 comments | | HN request time: 0s | source
Show context
stewbrew ◴[] No.23990645[source]
Separate ruby header files with type information? Seriously? What's the rational behind that? Is it just to make clear that the ruby interpreter doesn't really care about the type information and doesn't use it to improve the code's performance?

With all due respect, but IMHO this is too little and much too late.

replies(2): >>23990674 #>>23990677 #
learc83 ◴[] No.23990674[source]
"The benefit of having different files is it doesn't require changing Ruby code to start type checking. You can opt-in type checking safely without changing any part of your workflow."
replies(1): >>23990948 #
1. HideousKojima ◴[] No.23990948[source]
TypeScript allows this while also allowing inline type declarations, without breaking existing JavaScript
replies(1): >>23991029 #
2. hombre_fatal ◴[] No.23991029[source]
But it's not Javascript anymore.

Seems reasonable for someone to want types but not have to raise their own entire TypeRuby language + ecosystem + re-tooling.