David Mládek

I'd like to try to move this forward, so I've tried to compile the current state and list options for unifying the two macros. ### Event `[name: ,][target: ,][parent: ,]...

These are the default names of events. You could manually set `name: "anything"` in the macro invocations and that should get rid of it. The name does not have to...

LGTM, @jplatte can you take a look when you have some free time?

This should also fix #2737

Hi, this looks good to me. Can you just add an entry to the changelog please?

I may be wrong, but I think that without (compile time) reflection, the documented behavior is impossible? Or rather, the macro can look if the resulting type is named `Result`,...

All that would be needed for this is to support turning off `err` such as in `#[instrument(ret, err(off))]`. But maybe there is another way to make the intent clearer. Alternatively,...

We might want to deprecate it because curly braces are also used for evaluating const names and so the usage may become ambiguous to the parser. See #2837