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.

Sign up for GitHub

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

Jump to bottom

c.macroApplication of a macro annotation isn't typechecked #52

Open
xeno-by opened this issue Jul 26, 2014 · 1 comment
Open

c.macroApplication of a macro annotation isn't typechecked #52

xeno-by opened this issue Jul 26, 2014 · 1 comment
Assignees
@xeno-by

Comments

@xeno-by
Copy link
Member

xeno-by commented Jul 26, 2014

https://groups.google.com/forum/#!topic/scala-user/4yQtMKgK9-c
@xeno-by xeno-by self-assigned this Jul 26, 2014
@xeno-by
Copy link
Member Author

xeno-by commented Jul 26, 2014

This is an unfortunate implementation detail that I might get to fixing. In the meanwhile try doing c.typecheck explicitly.

SethTisue pushed a commit to scalacommunitybuild/paradise that referenced this issue Nov 21, 2017
@olafurpg
Remove range positions from expanded code.
90d409f 
This commit is a workaround for the fact that scala.meta macro
annotations don't compile with -Yrangepos enabled.
The option -Yrangepos causes scalac to validate that all start/end offsets
in tree positions follow a few invariants. These invariants enable
tools like Scala IDE to use binary search to quickly find trees.
However, the expanded trees by scala.meta macro annotations don't follow
these invariants. I haven't been able to investigate properly why this
is the case.

This commit removes range positions from scala.meta macro annotation
expanded code, enabling scala.meta macro annotations to not crash with
tools like like scoverage or scalahost were enabled. However, note,
those tools may need range positions to function properly.

Related issues:
- #181
- scalamacros#55
- scalamacros#52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xeno-by xeno-by

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xeno-by