1. Unless there is a single syntax, the topic will inevitably come up again and again. This does not necessarily mean that we need a single syntax, but this is a cost of the status quo (ie having both = and in) that has to be considered.
2. I think everyone said what they wanted to say. IMO it would be great if the key people in Julia could make a decision about this, either deprecate =, or in, or keep both, anything is fine, just have a clear indication of what is going to happen so that people could submit a PR for the documentation and the FAQ (if both are kept), or the base code (or one is dropped). Best, Tamas On Thu, Oct 29 2015, feza <mohamad...@gmail.com> wrote: > My only problem with `=` vs `in` > is that even the base julia code is inconsistent! Looking at one file ( I > can't remember which now) > it had both > i = 1:nr > and > i in 1:n > Again this was in the same file! Please tell me I am not being pedantic > when I saw this and thought this must be fixed if even the base is being > inconsistent. > > On Thursday, October 29, 2015 at 8:44:03 AM UTC-4, mschauer wrote: >> >> Do we want to give up on this topic? Then we should do so in an earnest >> way and close the case with a clear message, ideally after >> establishing if we want to add a style recommendation about the use of >> ``=`` and ``in`` to >> http://docs.julialang.org/en/release-0.4/manual/style-guide/. Currently >> the manual states in the control-flow chapter "In general, the for loop >> construct can iterate over any container. In these cases, the alternative >> (but fully equivalent) keyword in is typically used instead of =, since >> it makes the code read more clearly." >>
