Dotty Language Survey Results

[rjolly]

@SethTisue

and my impression is that most Scala programmers feel the same way

Not me. I’ve always thought we should not have discarded the ability to do myCode.filter(! _.isWhitespace) and have it still compile, like in Java or C.

[AMatveev]

@eyalroth

I think it really is a matter of opinion

I agree with you.
IMHO:
Indentation-blocks stems is terrible stuff for me when I work with larger dsl oriented block of code.
It is just a pain without any profit when I need to do simultaneously:

• refactoring
• copy\paste
• use language injection
• use more compact declarative style

There is opinion that good editor can help, I do not believe in that, there are always lack of good editors right here If you need work with multiple languages, for exampe changing between sql editor, diff tools, remote debugging I am not sure there will be good support for such stuff in nearest future. So I don’t like unnecessary grammar complication in such cases.

[AMatveev]

@curoli

Being able to omit brackets around a single expression is something completely different from being able to replace brackets by significant indentation.

Well said.
IMHO: If it were not so, yaml would supersede json in most cases(at least it is more simple comparison)

[som-snytt]

$ skala -Xsource:3
Welcome to Scala 2.13.2-20200410-000412-32c4e80 (OpenJDK 64-Bit Server VM, Java 11.0.5).
Type in expressions for evaluation. Or try :help.

scala> {
     | val x = 2
     |         + 3
     | println(x)
     | }
5

scala>

[LPTK]

@SethTisue

Consider the following program:

  val x = 2
    + 3
  println(x)

in Scala 2, this warns (“warning: a pure expression does nothing in statement position; multiline expressions may require enclosing parentheses”) and prints 2. But in Dotty, it prints 5, as expected.

I agree this is awesome, but it’s a little concerning that this:

  val x = 2

    + 3
  println(x)

prints 2 without a warning (at least in Scastie).

@rjolly

I’ve always thought we should not have discarded the ability to do myCode.filter(! _.isWhitespace) and have it still compile, like in Java or C.

This is not true. In Java, int i = 0 and inti=0 mean different things.