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
Issues we've patched, but still exist upstream
Issues that we've not patched, but are patched upstream, waiting for binary release to close
Issues that we've not patched and still exist upstream
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
ReferenceErroron(function(){return arguments[0];})(undefined);(Exceptions thrown on undefined returns from muli-arity CLJS methods) Return value of write calls not properly handled #3 Accessingundefinedargument via arguments causes error espruino/Espruino#1691"b"equivalent to"undefined"inpr"b" evaluates to undefined #15 Regex doesn't recognize difference between\bespruino/Espruino#1906Issues we've patched, but still exist upstream
esprit/src/esprit/make_rom.clj
Lines 9 to 18 in 1b55419
try/catchdoesn't return the value oftryon success - it must be wrapped in a fn and called with returnIssues that we've not patched, but are patched upstream, waiting for binary release to close
Math/floorbroken nil for Math/floor #7 Math.floor returns values equal to null espruino/Espruino#1865Issues that we've not patched and still exist upstream