>>53
This is a trade-off
the brilliance of this idea
It's a trade-off almost no one is willing to make, and it's a stupid idea. Requiring a minimum amount of whitespace around tokens is the worst possible turn any language definition can take. Tomorrow, some idiot
will come and say "I want to have identifiers with two spaces". If you're not willing to increase the minimum, it proves that the definition is flawed. Why the arbitrary limit? Why two spaces but not three? Why
n but not
n+1?
It's a worthless feature and your users will hate you for forcing them to always hit the space bar one more time than necessary (because no one in their right mind would put a space in the middle of an identifier).
Look at you: willing to train your eyes to do something completely stupid just to justify misfeatures, but unwilling to train them to do something for a good end.
Less whitespace==more code on screen.
More whitespace==more clarity
Optional whitespace==I have the choice to add code or add clarity
Mandatory whitespace==I have no choice but to add whitespace even if it's clear