The answers for the examples given near the end of the article are often present in language documentation. You can dig around and find the answer or you can sp

The answers for the examples given near the end of the article are often present in language documentation. You can dig around and find the answer or you can spend two minutes and write a test or you can crash/debug later. In any case, you'll eventually find the answer. The real issue is that programmers new to a language are unlikely to even realize there's a semantic boondoggle in a given situation. Had they read all of the documentation, perhaps they would - but that's obviously not what most people do. Adding more pages to the documentation just to collect all semantics in one place wouldn't seem to make it more likely that a new programmer is going to read and properly understand their implications. I don't think you can solve the problem of inexperience with additional education, but it's a common idea in academic circles.