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.typecheck is unreliable #75

Open
xeno-by opened this Issue Nov 19, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@xeno-by
Member

xeno-by commented Nov 19, 2015

Our initial implementation of macro annotations includes YOLO-support for c.typecheck: we do our best effort to call the typechecker so that it doesn't crash, occasionally losing precision because the typechecker resists our efforts.

When I released 2.0.0-SNAPSHOT with this limitation, my hope was that our experience with c.typecheck will let us understand it better and come up with a strategy that is consistent, reasonable and implementable in scalac. Unfortunately, it looks that my hope was ungrounded, because it's been two years and nothing satisfying has come up.

Related issues are:

@xeno-by

This comment has been minimized.

Show comment
Hide comment
@xeno-by

xeno-by Nov 19, 2015

Member

I will keep this issue open in case something comes up, but the current situation is:

  1. I don't know how to fix this in 2.x.
  2. An upcoming refresh of our macro system may let us view this question from a different angle.
Member

xeno-by commented Nov 19, 2015

I will keep this issue open in case something comes up, but the current situation is:

  1. I don't know how to fix this in 2.x.
  2. An upcoming refresh of our macro system may let us view this question from a different angle.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment