Skip to content

Conversation

@koic
Copy link
Contributor

@koic koic commented Jan 23, 2025

Follow up #189.

Currently, the default Ruby engine for the Playground is CRuby 3.2. https://try.ruby-lang.org/playground/

As a result, Try Ruby handles with CRuby 3.2.
https://try.ruby-lang.org/

This PR updates the default to CRuby 3.3, allowing Try Ruby to run in the latest available Ruby environment in browser.
The current Ruby version is 3.4, but the @ruby/3.4-wasm-wasi has not yet been released. Therefore, CRuby 3.3, the latest version available for wasm, is used.

This issue has been reported in the following issue and can be addressed independently:
ruby/ruby.wasm#567

Follow up ruby#189.

Currently, the default Ruby engine for the Playground is CRuby 3.2.
https://try.ruby-lang.org/playground/

As a result, Try Ruby handles with CRuby 3.2.
https://try.ruby-lang.org/

This PR updates the default to CRuby 3.3, allowing Try Ruby to run in
the latest available Ruby environment in browser.

The current Ruby version is 3.4, but the `@ruby/3.4-wasm-wasi` has not yet been released.
Therefore, CRuby 3.3, the latest version available for wasm, is used.

This issue has been reported in the following issue and can be addressed independently:
ruby/ruby.wasm#567
koic added a commit to koic/TryRuby that referenced this pull request Jan 23, 2025
This was noticed during ruby#191.

It would be preferable for newer CRuby engines, which allow the use of new features,
to appear more prominently at the top of the dropdown in the Playground.
https://try.ruby-lang.org/playground/

This PR rearranges the list to prioritize and highlight the newer CRuby engine.
@hmdne hmdne merged commit f0aca9c into ruby:master Jan 24, 2025
1 check passed
@koic koic deleted the cruby_33_by_default branch January 24, 2025 00:58
@eggplants eggplants mentioned this pull request Feb 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants