--
You received this message because you are subscribed to the Google Groups "Xtend Programming Language" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xtend-lang+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "Xtend Programming Language" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/xtend-lang/_0cDOOiRrFI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to xtend-lang+...@googlegroups.com.
- Lacking further functional programming helper classes. Functional programming is addictive so when you get started, you want to make the most of it, and with Xtend it's just not possible.
While it might help a bit for debugging of active annotations etc, I don't think that you are doing it right if you depend on generated code quality. All other java dialects generate bytecode directly and you would not expect decompiled version of it to be nicely looking java. Why for xtend in particular you expect to be able to move to java only environment with generated classes at any time?
Think about generated java code more as implementation detail and debug help, not as a lifeline to reduce possible exit cost.
- Generated code quality. It should be higher to make you fully confident to write code with it.
While it might help a bit for debugging of active annotations etc, I don't think that you are doing it right if you depend on generated code quality. All other java dialects generate bytecode directly and you would not expect decompiled version of it to be nicely looking java. Why for xtend in particular you expect to be able to move to java only environment with generated classes at any time?
Think about generated java code more as implementation detail and debug help, not as a lifeline to reduce possible exit cost.