Maciej Katafiasz

> There's a short doc on the topic. Quickest way I can think to do it would be to inherit (or compose a new object based on) Fill and override...

I see. Looking at it in a long structure that's heavily nested and mostly literal, I can see why it was done this way.

That's true, it does match `schema`, but `schema` documents it, and also `schema` doesn't need to match the rest of glom :). I do see the value of being able...

It depends somewhat on whether you want to access all fields, or named subset. For all fields, the `lambda t: tuple(t.values())` method is the most appropriate (it could also be...

@mahmoud: `STOP` was in fact the first thing I tried when I ran into it :). But it doesn't really abort either, just prevents further steps from taking place. For...

Ah, sorry, I got busy with another part of my project and I forgot to reply here. The output is a bit of a tricky area, since in the example...

@mahmoud: just a quick ping, is this clear enough, or do you need more info?

General help pointing me to where in the code it would make sense to start adding this, as well as enough pointers for whatever parts of the stack for me...

Would you mind pointing me to where that lives?

@tfeb: I think the fundamental issue here is that `LAMBDA-LIST` only looks at a single level of expansion, and any subpatterns are treated as Trivia patterns, rather than destructuring lambda...