4 ms·
What's status of static typing checking ?
by revskill 4y ago
What's status of static typing checking ?
- i_v 4y agoSorbet[1] is currently the most robust tooling available. It has a few rough edges and limitations but it otherwise works great for 90% of use cases. [1]: https://sorbet.org https://sorbet.org
- aledalgrande 4y agoAdd tapioca and it's much smoother
- _joel 4y agoOh lovely, there's this morning wasted :)
- berkes 4y agoBut Sorbet is also not part of the language, not part of the std-lib, and AFAIK there aren't plans to make it that.
- janus 4y agoProgress is really good, in this RubyKaigi talk there’s a great demo showcasing the official rbs with vscode integration https://youtu.be/4E4TRgMDYqo https://youtu.be/4E4TRgMDYqo
- Alifatisk 4y agoRBS is still suggested, but have you tried the Contracts gem?
- Fire-Dragon-DoL 4y agoA disaster so far. We tried using Sorbet for a component and we hit ab edgecase where we had to completely remove it. There is a lot of undocumented stuff, conflict between the right tooling and specifically for Sorbet, the lack of structural typing for a language like Ruby (you know, duck typing), makes it very unsuitable, nowhere near Typescript. When we tested, there was barely an experimental type checker for RBS, that was 1 year ago. Overall, we tried, had to bail out and stick to YARD. Horrible experience.