> > > Well, someone might already ask that by looking at `for` and `with` and > wondering if it works for `case`, `if` and `cond`. >
You are missing the point. :) for and with do not accept any expression. They have their own rules. They always had. I cannot write “for whatever do”. But if/cond accepts any expression, as is, no special cases. That’s the line I don’t want to (and we won’t) blurry. > This one is a good point, and maybe it would be a nice thing to make the > answer to that question a “yes” and just merge all the clauses using `and` > s. > Then it has to be made a special form and that has even further implications, so it is unlikely to happen either. And if we don’t make it, then if starts to look inconsistent (which was my point). To be honest, I can’t really tell the overall complexity of the change, and > neither what would the cost to compilation be (I suppose it’s big), but my > point is that maybe it is worth the try at least. > There is no performance cost. The cost is all in complexity and it forcing for us to do other changes in the language. If you can’t tell the complexity, you can trust the opinion of someone who can (and is describing it) :) But you are welcome to explore it. The language was made extensible for this reason. But I can say such change would not be accepted in core itself. > > -- *José Valim* www.plataformatec.com.br Skype: jv.ptec Founder and Director of R&D -- 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/CAGnRm4Kv4sDYnKeAgUS_baiTsgeXGjs428oThR%3DY%3De7ELnns1A%40mail.gmail.com.
