> > well, coming from someone (me) who read the docs but didn't adopt macroid, > I thought the docs were great. >
Thanks! You are more than welcome to elaborate why you did not adopt it though ;) > A short paragraph or two of a high level overview of the implementation > before diving into the samples would be nice. > I guess recipes have higher priority for now, but it would be interesting to see what aspects of implementation you are interested in (performance is different from implementation, as it has to be substantiated with benchmarks). I vaguely recall something about it using ?compiler templates? somewhere in > the docs. Sorry, there's still plenty I'm not familiar with in scala. > Do you mean macros? That’s the closest thing I can think of. They don’t affect performance, as the expansion is done at compile-time. Anyway, speaking of performance, this is clearly not my primary concern :) There is some wrapping going on here and there, most notably everything is wrapped into UI actions, and a <~ b is turned into TweakingOps(a).<~(b)(someTypeclassInstance). I haven’t observed any significant “snappiness” degradation, but again, somebody might want to benchmark this. Overall, Macroid should be reasonably close to the vanilla Java API. Obviously it’s not a good idea to use it for modern game-dev :) > But my main concern was the implementation and runtime performance. > Admittedly, I don't want to type tilde a lot either but that's more of a > minor note. > Not sure if you saw this coming, but could you suggest any alternatives to tilde? I’m happy to introduce aliases. Nick > -- 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.
