03:33 <emilbayes> why is this illegal? https://is.gd/XGdQDM

03:36 <jemc> it's just a design choice that was made in pony early on - the names of methods, fields, params, and local variables in the same entity aren't allowed to shadow eachother - the idea was that such ambiguity tends to result in subtle bugs

03:39 <emilbayes> jemc: Oh okay, was just caught by it in my iterator stuff. List has a constructor call `from`, which means that can't be used for the range arguments

03:39 <emilbayes> I could go with the hack from' but ...

04:30 <jemc> yeah it'll have to be `from'`

04:30 <jemc> it's pretty common to get forced into making params have a prime

23:51 <ada[m]> Does pony have anything like python generators/list comprehensions?

23:54 <jemc> ada[m]: I think it's not quite the same, but filling roughly the same "role" of Python generators in Pony is the `Iterator` interface: https://github.com/ponylang/ponyc/blob/master/packages/builtin/iterator.pony

23:55 <jemc> and there's a nifty package for doing various transformations on iterators that are similar "in spirit" to list comprehensions: https://github.com/ponylang/ponyc/blob/master/packages/itertools/itertools.pony

23:59 <jemc> the gist is that an `Iterator` is a stateful object that gets mutated to "point to" the next element in whatever you're iterating over, with `next` being called repeatedly to return the next element

23:59 <jemc> we don't have `yield` keyword from python or anything like it, because we don't have continuation passing at all, really