Roslyn VB.net Coding Guidelines

[AdamSpeight2008]

The current coding guidelines are C-centric, with no or very little guideline for VB.net contributions, for projects within the .NET Foundation that use the language within their project. Thus lack of clear guidelines has and will cause friction between different opinions on stylistic aspects of the code / contribution, rather that the functional / semantic behavior of the code.

I'm working on implementing a VBnet Coding guideline. (Here)

[gafter]

This repo is not about Roslyn or code contributions. It is about the VB language specification.

[AdamSpeight2008]

@gafter This proposal primarily affects VB.net contributions to Roslyn, hence make more sense to place the discussion in the vb repo, where those interested in adding features or changes to the vb language are.
It will aid those contributions to be less about stylistic aspects of the code, and more it semantic functional merits / issues.

[AnthonyDGreen]

Great work, @AdamSpeight2008 have you sent a PR for those guidelines?

I kinda wish we used at least a

tag even on private methods. Especially in the binder where things aren't often clear, E.g. BindValue vs BindExpression.

[AdamSpeight2008]

Also see #15

[AdamSpeight2008]

Pull Request #252