The appropriate use of namespaces and developer discretion would be needed to ensure you don't F up your other code. If you want a switch that checks if one st

The appropriate use of namespaces and developer discretion would be needed to ensure you don't F up your other code. If you want a switch that checks if one string is contained in another, you don't modify the switch syntax. You make a switchContain. And you know what "for (x) in Y {;;some more code here}" means the same way you know what "x= someFunc(a,b,c)" means. You look it up. Of course it is best if the developer uses good names and comments so you can make a good guess by looking at it. Yea it's hard, and yea it's dangerous. All powerful things are. I don't like being told I can't have something because you think I am too stupid to use it safely. Some people won't be able to use it, and everyone at one point will be too inexperienced to use it correctly. But thats why you layer the more common languages on top. And if you are running an enterprise shop where you can't guarantee the quality of the maintenance developers, don't let your developers use it. etc... Because it's too powerful is not a very convincing argument for me.