Benoit Daloze

Link: Discussion about adding gem platforms based on RUBY_ENGINE: https://github.com/rubygems/rubygems/discussions/5988 (from https://github.com/rubygems/rubygems/issues/5984)

I think this PR looks good now, except that `Immutable::Object` and `dup`/`clone` should be removed, in favor of some mechanism to integrate with the "is deeply immutable -> return self"...

> @eregon by the way `Immutable::Object` just uses existing methods for immutable dup/clone. Should we consider reworking those usage with whatever "flag" we end up with? Because it seems any...

> @eregon Do you have any thoughts on what core classes are candidate for being immutable classes? https://gist.github.com/eregon/bce555fa9e9133ed27fbfc1deb181573

What I have seen multiple gems do is stick to a previous release of simplecov, like 0.21.2, that's another possibility. E.g. https://github.com/notEthan/jsi/commit/35e9b5fbe3f485f58fffebd7ab6d395fabac9846

Given that `Bundler.require` exists and is used e.g. by Rails, I think it's a fairly well-known expectation that all gems don't do heavy processing or e.g. add TracePoints while they...

> ruby -rdebug some_script.rb OTOH using `rdbg ...` for that use case seems good enough, so probably no need to treat `ruby -rdebug` any differently.

Thank you for the report. From that behavior it looks like Dir#each automatically rewinds just before returning. It should be trivial to fix, we just need to verify that is...

Actually it's the opposite, Dir#each rewinds before starting to iterate: https://github.com/ruby/ruby/blob/dddf62426b7a384715dd558773723ecbdfa37a11/dir.c#L844-L859

I think that should be done manually, like: ``` jt --env ENV build graalvm=$(jt mx --env ENV graalvm-home) mv "$graalvm" DEST ``` Mostly because the graalvm layout is soon to...