Evgenii Kotelnikov

Good one! We should put a few examples like this under "Recursive acronym".

It feels like it belongs here for sure. But technically it's not an example of self-reference itself, rather it talks about it. Unless there is a mention of the book...

Hi, It would certainly be great to get rid of untyped macros, but I can't think of how to do it right now. To make your solution work, we would...

> How do you know anyway—with the current implementation—that it’s not `point(Some("foo").toString + "bar")`? That's how rewriting works — we start with the most nested subexpression. Basically, the whole expression...

Another issue is that we need higher-kinded type as the argument. I seem to remember, that `c.WeakTypeTag` didn't work for that.

The first one. Method invocation is represented somewhat like `Apply(Select('Some(Success(42))', 'getOrElse'), List("foobar"))`, so again, we start with the most nested subexpression: `42`, then `Success(42)`, then `Some(Success(42))`, that gets rewritten as...

Oh, cool! I'm not sure about the error. Looks like the whole expression is typechecked at some point (you'll get the same error message without the annotation). Generated code is...

Is that it https://issues.scala-lang.org/browse/SI-7461 ?

@stanch Could ypu please put up some examples of macro-annotated workflows? Or, even better, revise some of the examples in the current specs. I don't think anybody actually uses `scala-workflow`,...

@stanch To clear things up about the `typeCheck(tree, scope)` function: - The purpose of the function is to decide whether or not `tree` is lifted to a current workflow (with...