Closed joanlopez closed 1 month ago
I prefer that you do a merge commit here directly with the master branch from goja.
In this way the next time this code gets changed you don't need to cherry-pick and merge conflict fix changes.
Given how common it is for fixes or even feature additions to touch across multiple places, making it easy to not have merge conflicts seems like a must if we want to do this more.
I prefer that you do a merge commit here directly with the master branch from goja.
In this way the next time this code gets changed you don't need to cherry-pick and merge conflict fix changes.
Given how common it is for fixes or even feature additions to touch across multiple places, making it easy to not have merge conflicts seems like a must if we want to do this more.
Sure, of course! Like now? 🤔
Yeah and also the "merge pull request" so again .. git can figure out the merge conflict resolution later
Added support for separators in numeric literals.
Improved support for Unicode code point escapes (\u{...}) in regexes.
Improved number parsing compatibility.