Analyzer should catch dangling [Foo] references in dartdocs

[Hixie]

No description provided.

[scheglov]

There is some work in progress, which was not actually finished.
https://codereview.chromium.org/1530993002

[pq]

Given the possible (undesired) impact, maybe this should be a lint?

[pq]

cc @bwilkerson : what do you think about migrating this to a lint?

[pq]

@scheglov : how do you feel about us moving this over to a lint?

[bwilkerson]

Sorry, I missed the earlier ping.

I think that, hint or lint, we need to clean up the false positives as much as possible first.

I don't remember: are we currently treating square brackets within code as references and trying to resolve them? I don't think we want to do that, whether for this rule or for anything else (like navigation or refactoring). So I think we should take care of that problem independent of what happens to this rule.

[scheglov]

@bwilkerson We remove code blocks while resolving comments.

[Hixie]

If it's a lint, it would actually help with removing false positives, since we could turn it on only when we're specifically looking at this.

[pq]

Closing in favor of the lint request, in progress and tracked yonder: #57330.