Types will be part of Ruby 3 stdlib source
twitter.com
Types will be part of Ruby 3 stdlib source
1–10 of 216 posts
Re: Types will be part of Ruby 3 stdlib source
#2when Ruby 3.0 will be released? 2022 Christmas?
Re: Types will be part of Ruby 3 stdlib source
#3when Ruby 3.0 will be released? 2022 Christmas?
2019?
Re: Types will be part of Ruby 3 stdlib source
#4Nice! Reminds me of crystal[0], the LLVM-compiled ruby-alike language.
Re: Types will be part of Ruby 3 stdlib source
#5It looks like they've conflated type with class. If so, that's the antithesis of duck typing. The impedence mismatch to Ruby seems to me an overwhelming contraindication.
Re: Types will be part of Ruby 3 stdlib source
#6Very cool! I didn't think this would happen, as Matz has expressed disinterest in adding type annotations. However, keeping an open mind and reconsidering one's positions are the hallmarks of a great leader :D
I worked on a summer project to add type annotations to Ruby. Didn't get very far since I ran into some challenges with the internals of the parser and the parser library, Ripper. I'm extremely interested in seeing how the Ruby team designs the type system. It'll be gradual, of course, but also it'll be interesting what adaptations they'll have to make to accommodate existing code. JavaScript relied on a lot of stringly typed code, so TypeScript added string literal types. Perhaps Ruby's dynamic, block oriented style could lead to some interesting decisions in the type system.
Not to mention, the types will most likely be reified as per Ruby's philosophy.
Super excited for this. Between the JIT and types, Ruby could definitely see a renaissance in the near future.
Re: Types will be part of Ruby 3 stdlib source
#7Very cool! I didn't think this would happen, as Matz has expressed disinterest in adding type annotations. However, keeping an open mind and reconsidering one's positions are the hallmarks of a great leader :D I worked on a summer project to add type annotations to Ruby. Didn't get very far since I ran into some challenges with the internals of the parser and the parser library, Ripper. I'm extremely interested in se…
Indeed Sorbet does have literal types for strings and Ruby symbols.
We're still figuring out the details and converging on a common type system for Ruby3, but we've found them super useful, as you rightly point out!
And +1 on the Ruby renaissance! Super excited about all the exciting things that are currently being built!
Re: Types will be part of Ruby 3 stdlib source
#8I recommend whatching "Ruby3: What's Missing?", a presentation Matz gave earlier this month:
https://www.youtube.com/watch?v=cmOt9HhszCI
This might be misleading. That is, jump to around the 29 minute mark where he talks about the type profiler and .rbi file stuff.
Re: Types will be part of Ruby 3 stdlib source
#9It looks like they've conflated type with class. If so, that's the antithesis of duck typing. The impedence mismatch to Ruby seems to me an overwhelming contraindication.
Do you have any reference to any documentation of how they implemented types?
Re: Types will be part of Ruby 3 stdlib source
#10It's an interesting turn of event that Ruby, Python and JavaScript are all getting types.
Meanwhile, I've gotten myself more and more into Clojure. Which now that other dynamic languages seems to move closer to types, seems to be in a niche in that Clojure is moving further away from types.
It'll be interesting to see what happens at both extremes and in the happy middles.