Skip to content
This repository has been archived by the owner on Jun 22, 2021. It is now read-only.

Use of reader literal ref unintuitive #22

Open
jonpither opened this issue Apr 8, 2017 · 1 comment
Open

Use of reader literal ref unintuitive #22

jonpither opened this issue Apr 8, 2017 · 1 comment

Comments

@jonpither
Copy link
Member

When I use the ref literal pointing at the result of a ClojureScript expression, it doesn't work as expected. For example, what should happen in the below case:

{
config (aero.core/read-config "config.edn" {})
foo (println #ref [config :some-item])
}

Even if some-item exists in the config, the above will not print it out. This is because resolve-references happens against uneval'ed code.

Makes me think resolve-references is happening at an incorrect stage?

@SevereOverfl0w
Copy link
Contributor

This requires #ref to be factored into the topological sorting system. See aero for how this can be done. It's quite complicated.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants