Upstream Espruino Meta Issue

[kiranshila]

I'd like to keep an issue open for the things we do that "patch" inconsistencies in the Espruino interpreter. The less we have to do to the compiled CLJS, the better I think. So if we close issues that "fix" bugs but don't really fix the interpreter, we should note that those bugs really still do exists and once they get fixed upstream, revert our change and really close the issue.

Issues we've patched that are also patched in upstream, waiting for binary release to revert our fix

• [x] ReferenceError on (function(){return arguments[0];})(undefined); (Exceptions thrown on undefined returns from muli-arity CLJS methods) #3 https://github.com/espruino/Espruino/issues/1691
• [x] "b" equivalent to "undefined" in pr #15 https://github.com/espruino/Espruino/issues/1906

Issues we've patched, but still exist upstream

• [ ] All of the regex edge cases, like #2 but there are a lot of them. See https://github.com/mfikes/esprit/blob/1b55419221f83eab811728f94a3e2219ece089d3/src/esprit/make_rom.clj#L9-L18
• [ ] try/catch doesn't return the value of try on success - it must be wrapped in a fn and called with return

Issues that we've not patched, but are patched upstream, waiting for binary release to close

• [x] Math/floor broken #7 https://github.com/espruino/Espruino/issues/1865

Issues that we've not patched and still exist upstream

• [ ] #17
• [ ] #28