propensive

4 ms·

1.
by propensive 12y ago
We discussed this with Typesafe and Martin in advance of the announcement for exactly that reason. Notwithstanding the reasons for forking the compiler, the last thing we want to do is fork the community too. This is a community project, an
2.
by propensive 12y ago
I think there is a lot of Scala usage you perhaps don't see. As an example from the corporate world, at least six major international banks (probably more) are doing a significant amount of their development in Scala, some with teams i
3.
by propensive 12y ago
Don't focus too much on the relevance of the Typelevel fork to the Typelevel libraries. The people involved (myself excepted) work on the Typelevel libraries, and consequently have particular interest in the features they benefit most
4.
by propensive 12y ago
We've tried to avoid creating a "drama"; that's not the intention at all. But we want to attract other developers to our experimental fork, so that if you want to use new and exciting features, or contribute your own, yo
5.
by propensive 12y ago
Compiler plugins are powerful, but still too limited. We can't change parsing rules with a compiler plugin, for example. There are also potential compatibility issues with using some set of compiler plugins, and there's a performa
6.
by propensive 12y ago
> I don't understand what features they want to add beyond type lambda's, singleton types, and literals for bytes / shorts. We have more ideas on the table beyond these three, but Miles will go into more detail about these