Olivier Delalleau

> The best option seems to be method D, immediately following `eval:` with a quoted string, without putting a space in between. > > But I don't have a clue...

> Any update or workaround on this? I prefer to use tuples instead of lists in my configs for their immutability. Unlikely to be added any time soon unless someone...

> With that workflow, the resolver seems not to do anything. Instead, the conversion to a `dict_config = OmegaConf.structured(config)` converts the tuples to lists. I see -- I'm afraid I'm...

> Is there any update on this? > > Would [this ](https://stackoverflow.com/questions/6027558/flatten-nested-dictionaries-compressing-keys) with `separator='.'` be a first start to such a solution? This is unlikely to make it into OmegaConf...

> Many times I would like to be able to access the last element of feature layer lists - It makes everything so much easier. You can still do it...

> is somehow possible to incorporate those resolvers inside list literals? something like that: > > ``` > layers: [${getindex:${layers_previous_model}, -1}, 32, 16, 4] > ``` Yes, this should work....

> ``` > a: > aa: 64 > > b: > bb: ${eval: '2 * ${a.aa}'} > ``` > > The above should work but it doesn't in my case...

> I have seen them but I don't see where my error is. After all I just use multiplication. You are most likely forgetting to register the `eval` resolver: ```python...

> Please consider removing the `eval` suggestion from the docs. I agree it'd be good to add a warning, but IMO it's a useful tip that's worth keeping in the...

@teocasse what if there existed a `oc.eval_num` resolver that would call `eval()` under the hood, but would refuse to do so if there is any aphabetic character within the string?...