It might be not exactly what you need, but we use macros on Android in SpecGine ( game engine my group works on - https://bitbucket.org/specdevs/specgine ). While it isn't maybe the best example, it works good enough for our use case, i.e. we heavily use macro
def withManager[T <: ComponentsSpec]: T with ComponentsManager which inspects how T is constructed and mixes in manager instance to use it within our Entity system. It works quite well with macros in 2.10 (SpecGine 0.1) and we still use it with 2.11 after simple porting (current master branch), without macro paradise. What is the problem you are trying to solve? Because reflection can solve many problems, optimal solutions might be different. On Wed, May 21, 2014 at 12:28 PM, David Pérez <[email protected]> wrote: > Does anyone know if reflection at compile time through macros has this kind > of problems? > > -- > You received this message because you are subscribed to the Google Groups > "scala-on-android" 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-on-android" 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.
