c.typeCheck doesn't see declarations from the current scope

[xeno-by]

A very thorough discussion: aztek/scala-workflow#2

Related SO questions: http://stackoverflow.com/questions/19379436/cant-access-parents-members-while-dealing-with-macro-annotations and http://stackoverflow.com/questions/19954776/scala-macro-annotations-c-typecheck-of-annotated-type-causes-stackoverflowerror

[xeno-by]

There's an interesting twist to this story. If one tries to typecheck something that refers to the type parameters of the annottee, these type parameters wouldn't be taken into account: aztek/scala-workflow#2 (comment)

[FlorianKirmaier]

since 2.0.0-M8 the situation is worse. The compiler crashes with the following error:
scala.reflect.internal.Symbols$CyclicReference: illegal cyclic reference involving object TNodeASDF

Here is a example: http://pastebin.com/raw.php?i=Svm11P10

[aparo]

@FlorianKirmaier you are using java 1.8.0-ea. How is it stable?
Kudos to you of using 2.11-M8 on Java 1.8.0-ea :-)

[xeno-by]

Thank you! I'll try to take a look today.

[xeno-by]

@aparo Yeah, I can reproduce the error. I'll see what I can do.

[xeno-by]

@FlorianKirmaier I get the same error in the most recent paradise for M7. When did it stop working for you?

[xeno-by]

I see now. This problem is a direct consequence of the fix I applied above. It only manifests itself when there's an import in scope, which is why I missed it in the first place.

[xeno-by]

@FlorianKirmaier @aparo Fixed the regression, started jenkins builds. The fix should be published with an updated 2.0.0-SNAPSHOT build for all supported Scala versions (2.10.3, 2.10.4-SNAPSHOT, 2.11.0-M7, 2.11.0-M8, 2.11.0-SNAPSHOT) within a couple hours.

[xeno-by]

Unfortunately I haven't made any progress here, so we won't have a fix in 2.0.0-final. Any ideas are very welcome!

[xeno-by]

I've merged this issue into #75 and will close this issue now. If this is a blocker for you, please let me know, and we'll think of something.