Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ruby 3.1 required? #222

Closed
digitalmoksha opened this issue Jan 20, 2023 · 1 comment
Closed

Ruby 3.1 required? #222

digitalmoksha opened this issue Jan 20, 2023 · 1 comment

Comments

@digitalmoksha
Copy link
Contributor

I was wondering, is it necessary to require 3.1, or could it be relaxed to 3.0? We're making the move to 3.0, not sure when we'll upgrade to 3.1
@gjtorikian
Copy link
Owner

Nope, sorry. 3.1 is firm.

The Windows RubyInstaller fixed a critical bug (imho) in 3.1: https://rubyinstaller.org/2021/12/31/rubyinstaller-3.1.0-1-released.html

In particular the ruby and gem platform is now x64-mingw-ucrt instead of x64-mingw32 and the MSYS2 package prefix is now mingw-w64-ucrt-x86_64-.

To make my life easier and not have to keep in mind how platform strings change, I want this to be availabile for 3.1 and above. 3.1 also has a better JIT and async improvements.

In my opinion, just make the jump to 3.2, rather than stopping at 3.0.

Repository owner locked as resolved and limited conversation to collaborators Jan 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@digitalmoksha @gjtorikian