Re: Re: Setting positions for annotation generated trees

Hi!

Good error messages for macro expansions are hard, because it's usually
hard to automatically classify/position parts of expansions. However, it
might very well be that there's a heuristics that works for an important
class of use cases.

Could you give an example of how you would the compiler to calculate the
positions for your use case?

Cheers,
Eugene

On 16 August 2015 at 18:07, Torsten Schmits <[email protected]>
wrote:

>
> update 2: Noticed that I could cast internal.util.Position to
> c.universe.Position, and similarly for SourceFile.
> Creating those from scratch led to a completely satisfactory result,
> although using `atPos` somehow screws it up, while it works great when
> reflecting `setPos`.
> Anyhoo, I still have to calculate the positions manually, would be nice to
> have this done by the compiler.
>
> --
> You received this message because you are subscribed to the Google Groups
> "scala-language" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "scala-language" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.