hmdne

I'm quite sure this is related to #2249.. unsure though, may be a garbled $nesting

We now cache Opal.ancestors: https://github.com/opal/opal/blob/v1.2.0/opal/corelib/runtime.js#L1293-L1295

Further discussion will be needed for this PR, as maybe allowing for multiple bridges is not the best idea.

Related to #2235 - the 5aad139c7fcc92f4b5f7bd4412987843db535698 commit.

If you use the Zeitwerk pattern it happens _all the time_ (as can be seen from the `performance` task). The only situation which we can't optimize fully for is the...

Adding a milestone. But at worst we won't ship it.

This bug should go hand-in-hand with #2241.

The issue with this is that all String methods and alike should return a mutable string value and none of them do - which, on the other hand, is good...

Possibly an issue related to Native refactor: #1236

Regarding the String refactor, I would say that JS String could be bridged to Native::String which could have all methods the current String has (for example abstracted to a module)....