Git is a wonderful piece of software. I just see how easy it is to fix old mistake on commit message. I needed to correct misspelled emails and names of author, committer and “signed-off-by” in all commit messages on a source tree. Using filter-branch make it a piece of cake.
I am learning Scala.
I am sad to see that, again, like OCAML, like Rust, like CoffeeScript, Scala does not like the return statement. It is implicit as the evaluation of the latest expression in a block.
I am not really conviced by YAML over JSON. For me, it has the following advantages: Easy to read information is not lost in a sea of “<” and “>” like with XML I actually don’t like abiguity in json…
Some languages allow, or even force you, to declare your return statement in your function without any visual difference, only by being the last statement in the function. This is what we can call implicit return.
This article gives 8 reasons on why this is a bad design and should be avoided at all costs for general code, and give the only acceptable case where return might be avoided. For readability and maintainance sake, always use the return keyword of your language in your functions. Always.