I think @Libman and @gemath are on to something in suggesting that the
programmer should be able to decide how to handle insensitivity. To help Nim's
adoption, I'd say by default the compiler should generate warnings when
"insensitivity is detected", but you could later switch warnings off
--warning[insensitivity]:off
Run
(leading to current behaviour) or turn them into errors
--sensitiveMode:on
Run
And more fine-grainedly with some module import pragma:
import {.insensitively.} foo, bar
Run
Helping the "sensitive-minded" newcomers would be a PR win for Nim: It would
send a clear signal that the customer's voice is being listened.
I don't see voting in this forum relevant, because the results would be heavily
biased; For every active Nim user in here who is already used to syntax
insensitivity, there are 10000 potential Nim users out there who are not used
to it. You should rather ask them.
Personally I would rather see stripped-down stable 1.0 later than a bloated
unstable 1.0 sooner.
