each and first about ast HOT 7 CLOSED

You can do child, = *node. If this is not in the docs, it should be.

When do you use to_a.each?

from ast.

hmm, i didn't know you could do that. Frankly looks weird, rather use my first.

each off course to go over children. you're saying i shouldn't have to. And maybe when i switch to the instance variable an your processor i won't. But now i still do and it seemed a sensible thing to have in there.
But i seem to be receiving a more is less attitude , yes ?
Always surprises me in ruby projects, ruby being known for having 7 ways of doing anything, but ok, i get it.

from ast.

you're saying i shouldn't have to

I'm not. I am specifically asking what your use case is, because I have no idea what is it. I.e. children are usually heterogeneous; what common action over them is desirable?

from ast.

ok, maybe the question was slightly ill formed then.
Because the answer to your question was so obvious.

If you're asking why i need to iterate. Other than off course, because i have a collection.
To process them.

from ast.

Like if you have a (list) or a (hash)? Yeah, that's reasonable. I would accept a PR with each.

from ast.

sort of, i have an s(:expression_list , exp1 , exp2...) which is inside all statements, so common.
But i'll try that Processor with a stack now.
The code i'm talking about is temporarily here btw of almost nothing

from ast.

So, that processor / instance approach worked.
Quite like it even, so in total the switch to ast has bee great :-)

from ast.