Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

c.reify behaves differently from c.universe.reify #5999

Closed
scabug opened this issue Jun 28, 2012 · 3 comments
Closed

c.reify behaves differently from c.universe.reify #5999

scabug opened this issue Jun 28, 2012 · 3 comments
Assignees
Milestone

Comments

@scabug
Copy link

@scabug scabug commented Jun 28, 2012

This happens because c.reify uses c.mirror, but c.universe.reify uses c.universe.mirror (which, for one, bails on packageless classes).

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jun 28, 2012

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jul 3, 2012

@paulp said:
I ran into this the hard way, and it was brutal. If the standard thing to do when one is writing a macro is to start with "import c.universe._" then right away we have "reify" and "c.reify" doing different-but-the-same things -- and I have a feeling there is more where that came from. Can something be done to limit the frequency with which same-named almost-the-same identifiers arise?

@scabug

This comment has been minimized.

Copy link
Author

@scabug scabug commented Jul 20, 2012

@scabug scabug closed this Jul 20, 2012
@scabug scabug added this to the 2.10.0-M5 milestone Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.