In my opinion it should be an error or at least a warning.
I'm not a big fan of nim's behaviour, but I don't think it's any worse than what other languages do.
Them being the same is worse. I agree that both are pretty darn bad, but it's also pretty clear to me which is worse.
Having them be the same, by far.
Having names with certain similarity be prohibited in the same scope is a bit excessively controlling but sensible. Allowing them but treating them as equivalent is just plain bad. If I named them differently then either: (1) I made a mistake, or (2) I intended them to be different.
That's the same as saying "`a` and `A` should be the same variable", i.e. complete case insensitivity.
> It's a pretty bad code smell either way.
Very much so. We shouldn't encourage it.
I use same names with different styles to denote scope. I will be hosed then.
That would be a pretty hard sell. Any convenience argument falls flat to me.
If you're using Emacs to begin with... well there is little reason to complain about the default behaviour of functions and keybindings.
http://nim-lang.org/0.11.0/manual.html#lexical-analysis-iden...
This just killed my excitement for this language. That's really surprising to me that they would choose to enforce indentation Python-style, but would then allow this kind ambiguity in naming.
grep and emacs isearch-forward are such great tools for quick code searching and this will break them. I guess text search (and replace) tools could grow nim-mode options, maybe. I don't know, can someone convince me this is a good idea?