Supporting structured data (was: Re: bug-bash Digest, Vol 238, Issue 2)

2022-09-07 Thread Martin D Kealey
Some things do indeed come down to personal preference, where there are no right answers. Then Chet or his successor gets to pick. Keep in mind that most or all of my suggestions are gated on not being in backwards-compatibility mode, and that compat mode itself would be lexically scoped. With tha

Re: Supporting structured data (was: Re: bug-bash Digest, Vol 238, Issue 2)

2022-09-07 Thread Yair Lenga
Thanks for providing feedback and expanding with new ideas. I believe the summary is: ${a.key1.key2} - Static fields ${a.key1.$key2} - Mixed dynamic/static, simple substitution. ${a.key1.{complex.$key2}} - For complex keys that may contain anything ${a.key1[expr].key2] - expr is evaluated in num

Re: Supporting structured data (was: Re: bug-bash Digest, Vol 238, Issue 2)

2022-09-07 Thread Yair Lenga
Another comment: While it’s important to use “natural” access, I believe it is ok to have a command to set values inside the h-value. It does not have to be supported as part of …=… , which has lot of history, rule, interaction with env var, etc. I think something like: hset var.foo.bar=value