Skip to content

Conversation

@y-yagi
Copy link
Contributor

@y-yagi y-yagi commented Oct 5, 2025

This PR adds CRuby 3.4 and using it as default. This PR also bump js libraries to support CRuby 3.4. This PR includes the following commits.

  • Ignore warnings from gem_prelude. 02e51b1
    • With the latest wasm-wasi, the some warnings are shown. I assume this this is because the current usage of ruby.wasm on TryRuby don't consider RubyGems and fails to load it. But, this is just warnings and there are no other issues. And, it seems that this warnings would not be shown in Ruby 3.5. So I fixed to just silence those warnings.
  • Add Ruby 3.4 error message format to check the answer correctly 2036eab
    • The error message format has changed in Ruby 3.4. I added the error message format to an answer to check an answer correctly.
  • Add Ruby 3.4 hash format to check the answer correctly 17ce458
    • In Ruby 3.4, the result of Hash#inspect has changed({:mediocre=>2} -> {mediocre: 2}). I added the answer to match with the new format.

y-yagi added 4 commits October 5, 2025 13:12
With the latest `wasm-wasi`, the following warnings are shown on TryRuby.

```
`RubyGems' were not loaded.
`error_highlight' was not loaded.
`did_you_mean' was not loaded.
`syntax_suggest' was not loaded.
```

This warnings come from `gem_prelude.rb`.
https://github.com/ruby/ruby/blob/master/gem_prelude.rb

I assume this this is because the current usage of `ruby.wasm`
on TryRuby don't consider RubyGems and fails to load it.

We should change the structure of how to use `ruby.wasm` for fixing
this. But, this is just warnings and there are no other issues.
And, it seems that this warnings would not be shown in Ruby 3.5
ruby/ruby@4e303fd
ruby/ruby@e9dadf1

So I fixed to just silence those warnings.
@y-yagi y-yagi force-pushed the support_ruby34_latest branch from d8cc266 to 17ce458 Compare October 5, 2025 05:34
@y-yagi y-yagi marked this pull request as ready for review October 5, 2025 07:01
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.

1 participant