Get rid of procedure syntax about dora HOT 3 CLOSED

Not sure I agree with this: This shouldn't really be surprising coming from many other programming languages (e.g. Rust or Swift). I guess your main point is to discourage functions with side-effects. Not sure it helps that much since it only makes the definition more tedious to type and longer to read. It certainly doesn't discourage side-effects in functions with return values for example.

from dora.

I'd say my main point is consistency. it feels very weird (at least to me) that there is one syntax for functions of all types, except for functions with one "special" type, which gets a different, privileged syntax.

I agree on your point that dropping procedure syntax doesn't rule out side-effects in functions, but in my experience it helps nudging people into the right direction.

from dora.

If one takes fun procedure() { ... } at face value, it could mean all kinds of things to the uninitiated reader – the return type is inferred, it returns Object, it's dynamically typed etc. Having procedures follow the same rules as all other methods solves this issue.

Not sure it helps that much [...]

It did! As an example, one language that successfully made the change is Scala.

from dora.