CLJS Support #24
Draft
CLJS Support #24
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
WIP / very draft. exploring problems presented by running the lib in cljs.
Fixes #9
Rework of #11
problem 1:
https://ask.clojure.org/index.php/10372/is-it-possible-to-get-the-value-of-cljs-var-from-clojure-macro
notes
I'm pretty sure now that the way this library works is almost impossible to replicate in CLJS. CLJS macros don't have access to metadata or var's values at compilation time. A way around it would be to do all the work which the macro does at runtime, but the only way I can see that being possible inside EQL values is via a lookup of some sort. It's annoying that there's so much divergence between the two dialects in this regard.
Will be pausing this for a bit and see if inspiration strikes for another way of doing this.