personally I'd love to have CF say "b is undefined on a" when you try to do

a.b.c = 1

rather than being magically helpful 🙂 but I know that's been a feature of the language for lo these many times

I like this for the same reason I like

directoryCreate( path="/foo/bar/baz", createPath-true )

because I don't have to worry about whether

/foo/bar

already exists. The fact that I want

/foo/bar/baz

to exist provides enough context to the engine that I obviously want/need the parent dirs and it would be redundant for me to need to tell it.

yeah - I can definitely see why it was added. When you need to deep nest structs and don't want overly verbose code it makes it cleaner