Roland Fredenhagen

> Edgecase for variable access would be a multilayer closure. (there are two parent layers). this could be done by providing a scope index for outer variables? e.g. 0 would...

thinking if it makes sense to maybe allow to attach arbitrary metadata to instructions. (might be useful for breakpoints and such, and also all source code looks different, maybe line...

I guess using default for something like this wouldn't be too uncommon, looking at std functionality like `mem::take`.

@daxpedda should this be part of a general `skip` (would be a breaking change) and it would pose a strange problem in combination with `Copy`. Should this be allowed if...

It doesn't sound too bad to do, and you are probably right that it wouldn't be possible to emit serde's syntax with declarative macros, because string concatenation only works in...

@daxpedda, how would you want to do this syntactically, should we use the name `Serialize` and `Deserialize` I'm slightly opposed as they are not std traits, on the other hand...

Probably a good idea to stick with what we have for now, but maybe we can revisit the FQN for crate in the future, there are probably still some open...

One thing to check is verify which shells actually support different behavior here, e.g., fish won't honer us providing the space or not, but uses a list of characters to...

I think if we just extend `CompletionCandidate` to have a `should_space()` or `get_with_space()` don't care about the naming, the shell specifics shouldn't be an issue. Though it does mean, that...

> Looks like we just do a basic split:\n\nhttps://github.com/clap-rs/clap/blob/5efa52ad4501393d50e236d10a979313a61d4929/clap_builder/src/parser/parser.rs#L1164-L1166 so if we go the route of using trailing `,` in fish, we'd need to make the parsing ignore a trailing...