Interestingly, on Lambda the Ultimate[0] today I found an article[1] that
discusses some of this - the Three Laws of Programming:

- What you get right, nobody mentions it.
- What you get wrong, people bitch about.
- What is difficult to understand you have to explain to people over and
  over again.

D's spec on slices is covered by #3: "The difficult to understand stuff
is a real bummer. You have to explain it over and over again until
you’re sick, and some people never get it, you have to write hundred of
mails and thousands of words explaining over and over again why this
stuff means and why it is so. For a language designer, or author, this
is a pain in the bottom."

The article also suggests tagging the source with the compiler version it
was written for. Might be worth considering.

[0]: http://lambda-the-ultimate.org/node/4754
[1]: http://joearms.github.io/2013/05/31/a-week-with-elixir.html
-- 
Simen

On Friday, 31 May 2013 at 18:14:57 UTC, Simen Kjaeraas wrote:
>
> Interestingly, on Lambda the Ultimate[0] today I found an article[1] that
> discusses some of this - the Three Laws of Programming:
>
> - What you get right, nobody mentions it.
> - What you get wrong, people bitch about.
> - What is difficult to understand you have to explain to people over and
>   over again.
>

And how else should it be? Just think if natural selection worked some other way...