hmdne

Also... let's take a look at the visitor pattern that is used by parser and friends. We would need then to support wildcards, like eg.: ```ruby # dont_treeshake: on_* ```

Also @janbiedermann while this is related, we talked with @elia yesterday about things like, what if we extended the `parser` gem to find a magic comment like `# js_xstrings: true`...

To be resolved with #2274

I just rebased it onto the current master.

If I would to suggest something... maybe this could be a good idea: ```js if (typeof Symbol !== "undefined") { Opal.s = function(name) { if (typeof Opal.s[name] !== 'undefined') return...

I bet that you would fix it with changing $rblineX( to [Opal.s("rblineX")](

@Mogztter It has been a long time since this PR was started and things got very different. I think this is the way forward, but only in a compatible way....

And so, my proposal would be like this: first level is compiler support, so a compiler switch that would enable the new behavior. Second level is runtime switch, which would...

> How so? Do you mean that it would be better to start from "scratch" (i.e., start a new branch from master)? > Very possibly. master has diverged quite a...

Bumping an old issue, but I came upon this problem as well. First, I would advise against serializing things on client and deserializing on server using Marshal - that's not...