Types will be part of Ruby 3 stdlib source

Re:Types will be part of Ruby 3 stdlib source by viraptor on Friday April 19, 2019 @09:29AM (#19699414)

It depends what do the type annotations do. I'm not sure how perl6 does it, but for example in python type annotations are completely ignored at runtime, so don't have any impact. We'll see how much / for what does Ruby 3 actually want to use the type information. Sorbet on its own is unlikely to affect runtime either.

[ Parent | on HN ]

Re:Types will be part of Ruby 3 stdlib source by fjp on Friday April 19, 2019 @12:53PM (#19701020)

Going to keep praying for type/performance optimizations in Python so we can all get past the "python is slow" thing.

Async python is an absolute joy to develop with.

[ Parent | on HN ]

Re:Types will be part of Ruby 3 stdlib source by delaaxe on Friday April 19, 2019 @01:21PM (#19701259)

Care to elaborate which type of work you're doing and which libraries you're using?

[ Parent | on HN ]

Re:Types will be part of Ruby 3 stdlib source by fjp on Monday April 22, 2019 @10:19AM (#19719112)

Libraries:

aiohttp: web framework

aiopg: async postgres driver with SQLAlchemy support

asyncssh: async ssh library with SFTP capability

I generally work on CRUD microservices to automate some steps of a business workflow - activating/registering a resource with our vendors, generating and updating pricing, picking up new files off an FTP site and processing.

[ Parent | on HN ]

Re:Types will be part of Ruby 3 stdlib source by lizmat on Friday April 19, 2019 @11:05AM (#19700176)

Type checking is runtime, although if the static optimizer can figure out that a certain call will never work at compile time, it will throw a compile time error.

[ Parent | on HN ]

Re:Types will be part of Ruby 3 stdlib source by joesb on Monday April 22, 2019 @04:43AM (#19717427)

On the other hand, if the static optimizer can figure out that a certain call will always work at compile time, it can remove the runtime check for that part.

[ Parent | on HN ]