Can we reach this in other way?

[FrameMuse]

I'm not a conservationist, I like when my lovely language is evolving but I would like to avoid unnecessary and ambiguous changes.
Sooo, is there a way to get this exact behaviour in a status-quo JavaScript?

This is better if you write about it more in README.md to have a contrast between a status-quo solution (if it exists) and your proposal-solution. I'm not seeing this right now, but from what I saw I could think there is workaround for this already.

Is this change to a JavaScript realy what we need or creating a library would be enough?

[FrameMuse]

I just realized that motivation is kinda describing it.

[legendecas]

The section on prior arts expanded on this so I will close this.