coverage of gloms (track unevaluated child sub-specs) about glom HOT 3 OPEN

once this first phase is working, probably second phase is to set a global variable that means "hook all gloms in the system and accumulate a report"

-- similar to how coverage and cprofile work

in that case, each glom should keep track of the stack that allocated it so you can get a report like this

glom (module x, line 123) ..... coverage 90%
glom (module y, line 456) ..... coverage 70%

from glom.

Yeah I could see this being integrated into Inspect's functionality as a flag. Could also see it being a global thing that one would want to set once for all gloms during the test suite, too. The latter is probably the more common case, but there have definitely been times where I just wanted to know, in an interactive setting, which parts of the spec were being hit.

from glom.

this seems really dependent on having separate "compile" and "execute" walks of the spec

from glom.