CLJS613 application #43
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-- some functions added to satisfy line number errors.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've finally tracked down the issues to try/catch and surgically bisected out the relevant changes that were made to the master fork of Clojurescript for
CLJS613.This unifies the
try/catchform and brings cljs-in-cljs up to current conventions, allowing cljs-in-cljs to run such code.clojure@24bb5b7
This was also applied against of the
compiler.cljsandanalyzer.cljs.This allowed
core.asyncto run for the most part, except forjs-modfor which I am working on a patch for.