Earlier quoted context omitted.
> why would you need parens when you know the for starts the next nested loop Well that's the thing, I don't know the "for" starts the next nested loop because there's no indicator for that, and aside from that it's harder to see it at a glance. Nested loops have a colon, line break and deeper indentation inbetween, here you get nothing. To me it feels like it breaks Python's own rules: the language omits curly brace…
> Well that's the thing, I don't know the "for" starts the next nested loop because there's no indicator for that `for` is a keyword in the language - you know that the `for` starts the next loop by the same reason you know `for` starts any loop. The remainder of your complaint makes zero sense. You expect us to sympathize with an archetype (you) that is familiar enough with the language to know what a `for` loop is…
Mojo is available for local download
191–193 of 193 posts
Re: Mojo is available for local download
#192Earlier quoted context omitted.
> Well that's the thing, I don't know the "for" starts the next nested loop because there's no indicator for that `for` is a keyword in the language - you know that the `for` starts the next loop by the same reason you know `for` starts any loop. The remainder of your complaint makes zero sense. You expect us to sympathize with an archetype (you) that is familiar enough with the language to know what a `for` loop is…
Readability is about more than knowing keywords, if you can't even agree with that and the syntax consistency issue I don't have much more to say.
the goal posts have been moved; your comment:
> I don't know the "for" starts the next nested loop because there's no indicator for that
my point: there is no other role that the sequence of characters `for` can play in python (because it's a keyword) so you have all indication that you need.
Re: Mojo is available for local download
#193It honestly feels a lot like writing C++ with Python syntax. Still a lot missing, but excited to see where it goes.