These are chat archives for non/algebra
forallthat eliminate the closures completely.
coreis about the capabilities of objects and the macro machinery, while
libraryprovides the implementation of mutable and immutable versions of hash maps, sets, and the like.
corepart, I'm open about splitting it in a different common project.
... can write Scala code in a quick'n'dirty imperative way....
I agree that this is the best answer, for science and engineering. In the past, C/C++ tried to be the way to go, but is really too much if it's not your main job - same for quants in finance. But python/matlab are/were based on C/C++ but hid the details unless really needed. I think the same is needed for scala, except that the division has to be self imposed; unless, of course, there's more than one scala ;)