Question: Should analyzers for VB.NET be written in VB.NET?

#### Pro C#:

1. Wider pool of potential maintainers (but see point 4)
2. Pattern matching (as of this writing)
3. Extending an existing analyzer (but see point 5)

#### Pro VB.NET

4. VB.NET programmers are more familiar with the language, and are thus better suited to write and maintain an analyzer.
5. Analyzers don't really lend themselves to cross-language extension -- the Roslyn `SyntaxKind` enums and the syntax node classes are different between languages.

The specific analyzer that I want to write for VB.NET already exists for C# [here](https://github.com/Microsoft/RoslynClrHeapAllocationAnalyzer), with a [request for VB.NET support](https://github.com/Microsoft/RoslynClrHeapAllocationAnalyzer/issues/62).

The [only guidance I was able to find specifically about writing analyzers/code fixes **for** VB.NET](https://github.com/dotnet/roslyn/wiki/How-To-Write-a-Visual-Basic-Analyzer-and-Code-Fix) (by @AnthonyDGreen) describes writing them **in** VB.NET.

ping @AnthonyDGreen @bandleader @KathleenDollard