Nick

> > Is that it https://issues.scala-lang.org/browse/SI-7461 ? > > Yes, with a difference that compilation does not fail. @xeno-by should I submit a new one, or we reopen this one?

I know you are both watching that bug, but just in case—the reproduction is here https://github.com/stanch/paradise-bug. And now to something completely different. I realized this morning that by macro-annotating the...

I will put the examples in `readme.md` in my fork as soon as [1]—and hopefully [2]—is fixed. As for the usage, well, besides 90 stars that you already have I...

@xeno-by Maybe it can. To maintain the code here [1], I need a way to get the error description from the erroneous tree. I did a quick search through auto-completion...

@aztek Thanks! I kinda understood this, but your explanation makes it more clear. I am working on my idea with stubs and would like to start a discussion on the...

@xeno-by I just found a rather upsetting issue: ``` scala val x = Some(3) @workflow(option) val y = "asd" + x ``` fails during annotation expansion with `not found: value...

Damn... It started so nice... But what about ``` scala @workflowContext(option) def test = { val x = Some(3) $( "asd" + x ) } ``` ? This one doesn’t...

> We gotta traverse through the expression and find context/$ applications, how to reliably recognize that they're not locally-defined functions? Also, what if there're nested $/context applications or nested annotations?...

So here is the gist: https://gist.github.com/stanch/6421641 I think everything looks reasonable :) However, right now the implementation is blocked by the following: - No type args in macro annotations (https://github.com/scalamacros/paradise/issues/2)...

Oh, sure! I was thinking to allow annotation of classes (which would influence the code it their bodies), but somehow forgot the objects. Not sure why I had ``` scala...