eugene_burmako

5 ms·

1.
by eugene_burmako 8y ago
Prompted by a similar question on Reddit, I have written a comment on the history, the scope and the status of Scalameta: https://www.reddit.com/r/scala/comments/8g359q/macros_the_pl... .
2.
Twitter announces Reasonable Scala compiler with the focus on compilation speed(github.com)
13 points by eugene_burmako 9y ago|2 comments
3.
by eugene_burmako 10y ago
Author of Scala macros here. Here's a recent discussion on the future of macros in the brave new world of Dotty: https://www.reddit.com/r/scala/comments/4our5m/keynote_scala... .
4.
by eugene_burmako 12y ago
What kind of performance issues are you having in mind?
5.
by eugene_burmako 12y ago
Speaking of byte/short literals, we can already have a syntax for them with string interpolation. In fact, that's what is already implemented in Spire: https://github.com/non/spire/blob/ac12fd02180e3
6.
by eugene_burmako 12y ago
ClassTags were always thread-safe - they are simple wrappers over j.l.Class. TypeTags however were not, and that's supposed to be fixed in 2.11.0.
7.
by eugene_burmako 13y ago
Scala macros are different. We deeply respect the Lisp tradition, in which we are rooted, but we also accommodate and empower our language's values - static types and rich syntax [1]. The end result is admittedly less flexible, but it
8.
by eugene_burmako 13y ago
Hi, that's me who's doing macros for Scala. Martin & Adriaan have already commented on my choice of the project and its status within Scala, but I'd like to additionally elaborate on your other points. Speaking of target