> I just want to throw in my two cents. I don't think a warning should be > generated if there is no ambiguity about a name. >
Please re-read my replies and let me know if it is still not clear. The simple fact this feature exists, it means every time you are changing or reading code, you have an increased cognitive load because you are never sure what "hello" means. Even if there is no name clash in that particular case, since you can only know there is no name clash after careful examination. It is exactly the same case with the imperative assignment that was deprecated. Maybe you never relied on it, but the fact it exists, means that everyone reading your code and every code you read, needs to be carefully read with the consideration of their existence. > I find it a little difficult to understand why always warning is > preferable to warning conditionally for this one. > I have also explained in a previous reply how this will lead to more false positives and more undesirable situations if a conditional warning is implemented. -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4KUx5yKjWtusN9GGR4GgUxnR97Z%2BKJ3GkdfXC6vyuc8SA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
