Kurt Rose

better target-path

1

there was some prototyping of `scope[Path]` as a mechanism for tracking target path, but there are some flaws and also it eats a lot of performance for light specs (e.g....

just had a thought -- not sure if this is feasible but probably worth looking into it would be great if `[subspec]` simply preserved the laziness of the target it...

WIP: Pybay20 code

1

probably never merge

coalesce-along-list

6

```python context = [{}, {}, {'user': {'client': 123}}, {}] client = glom(context, Coalesce( ([Coalesce('user.client', default=SKIP)], T[0]), default=None)) ``` basically, you want to get the first element in a list which...

we don't want memoization of all inputs and outputs, because in general this would cause memory usage to balloon however, have the ability to do some amount of memoization would...

Macro + Compiler

4

just expanding ideas, getting some terminology out that can nucleate further docs / cookbook items and guide future development -- a "macro" or "glomacro" in the glom context is a...

Switching SKIP and STOP to exception control flow

2

agree we shouldn't modify Fill to respect SKIP and STOP.... maybe Match though?

STOP/SKIP raise StopGlom(), ContinueGlom()?

6

rather than scanning one level for STOP and SKIP literals, should instead STOP and SKIP have a glomit() which raises StopGlom() and ContinueGlom()? then, specs for which these make sense...

proofreading 20.7.0 docs

13

``` If either was not present, it would raise class:~glom.MatchError. class:object however is matched with func:isinstance(). Since it is not an value-match comparison, it is not required. ``` 

these all go off the truthiness of the result rather than raise or not raise GlomError