Hacker News Reader

I used OCaml before switching to Scala professionally, and I must say I prefer Scala's type system. It makes almost no space for errors/mistakes when you do things conventionally, like putting types on public members.

The idea of cleaning up the syntax a bit (XML, procedure, etc..) is great, but I'm not sure to understand what's "A better treatment of effects" (slide 44)? What's intended?

View on HN

Currently, Scala is an impure language.

There is some research going on how Scala can start checking and enforcing purity. Having an IO type constructor with the usual monadic convenience operations is one possibility, but people are actively looking into other approaches.

Thank you, I wasn't sure about enforcing purity, but now its clear :)

Reply on news.ycombinator.com