> The more I explain this, the clearer it becomes to me variables and > functions have no business in stepping on each other's namespaces. >
Except that classically a variable is simply a zero arity function with a shorthand creation syntax. OK, one more try. If I say `Mod.a`, then 1.4 (correctly) treats it as a call—I don't need the ()s. A bare function call means the current module. So could we also support `.a` as a function call in the default module? (I know the answer to this. But I wanted to trigger some lateral thinking on your part. Some part of me is sure that this () thing is a move in the wrong direction, and I'd really like to find the magic button to help you see it too) If you keep these warnings going forward, I don't think you should change iex—it should be consistent with the rest of the language. -- 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 elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/61d33cd3-23e8-4606-a27a-fb0bc9d7f1ad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
