> And changing it WILL break a lot of code... I don't even think that this > could be done without harm to Nim.
\--- In all honesty, a default is better as fixed state, with the ability to override to stateless if people want to use it like that. The argument that it will break current code is not relevant simply because the language is still pre 1.0. And its better to "fix" or create a better solution now, before people use it in production. * Search tools should generally become smarter anyway. And the Unix "tools" are all abominations anyway. As said before, this allows easy searching without relying on a external Search tool. I do not see the Visual Studio Code, Nim Plugin author overriding the default search ability. Same with all the IDE's. Small fish in big ocean... * It's just better than other programming languages. One does not need to be more advanced just for the sake of being advanced. When you import a function "foo_Bar" and accidentally write it "fooBar", the compiler simply spits out a error like every other language. And it takes 2 seconds to fix. In all honesty, i do not see any future languages adopting this feature because it simple brings little to the table but creates potential problems ( and actually has real world consequences ). Not without a ability to define rules for the imported modules. Especially if you work in teams! And no ... not all teams are coherent. Sometimes you can have mixed teams with experience programmers, lazy programmers, amateurs etc. Lets say i start pushing code to the nim core code. And i use my own style. It will simply irritate some people when they read the code because it keeps switching between styles. Let alone the disadvantages of searching in IDE, Editors, file based etc. Hell, even a basic Linux Grep does not work on Nim when people switch between use underscores and not. Its late, tired but lets put it this way. If there is no solution for this issue, it will keep coming up again and again. I see it plenty of time in the reddit programming topics where people simply can not understand the reasoning behind it and they see no advantages. And then the discussion became's about this again and again. Like i said before, my job is dealing with crap code all day. And stateless like this will simple make it even harder to deal with amateur or badly programmed code. Not everybody is a high level programmer that will follow a standard. At pure minimum there needs to be a standard rule set, that can be override / disabled for those that want to do so. Most people will follow the standard rule set or maybe tweak it to fit there style. Anarchy does not rule ;)
