I'm not sure if it's exactly the same, but you can see that a couple of the later comments there talk about "exception trees" and other types of annotations.
If that issue were addressed after ExceptionGroups were introduced, does that mean there would then be two types of exception-related trees layered over each other (e.g. groups of trees, trees of groups, etc)? It makes me wonder if there's a more general tree structure that could accommodate both use cases...
--Chris
Interesting, I commented on that issue - I think we may be able to solve it without adding more trees.
That said, we will have groups-of-trees/trees-of-groups. Already today, an exception plus its chained __cause__s and __context__s is the root of a binary tree of exceptions. The nodes of this tree represent the times that the exceptions were caught.
An exception group is a tree where the nodes represent the times when exceptions were grouped together and raised.
Irit