Problem matchers should support creating related diagnostic information

[kieferrm]

See #55120 for motivation.

[Gama11]

If I recall correctly, there were some plans to allow programmatic problem matching (which would solve a lot of other problem-matcher-related issues as well). Maybe it's easier to support it there instead of trying to come up with some way of doing it in a declarative fashion.

See also: #9635 (comment)

[ncannasse]

Can we can some update on this ? We keep hitting into Problem-Matcher issues because we have no programmatic control over it. Ping @dbaeumer

[alexr00]

It's not currently planned work or on the road map, but its something that we want to do at some point.
You can always see our iteration plan here: https://github.com/microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Aiteration-plan
And our road map here: https://github.com/microsoft/vscode/wiki/Roadmap

[GitMensch]

The workaround I currently apply for this is to explicit parse the second one as informational and then filter that out in the problems pane, but that is the wrong approach. Using a "child" approach would be the correct one - but that seems to be not possible currently.

@alexr00 said:

It's not currently planned work or on the road map, but its something that we want to do at some point.

That means it will be lost.
Can you please add this to back-log or the road-map?

[GitMensch]

While it may be obvious - as soon as the problemMatcher can define linked diagnostics, which is already available in vscode since 2018-03(!), then the documentation at https://code.visualstudio.com/Docs/editor/tasks#_defining-a-problem-matcher should be extended too.
I suggest to use the common "xyz defined here" diagnostic or gcc's "included from" as a sample.