Added: LDM Notes for Jan 9th, 2019

[agocke]

https://github.com/dotnet/csharplang/blob/master/meetings/2019/LDM-2019-01-09.md

Agenda

1. GetAsyncEnumerator signature
2. Ambiguities in nullable array type syntax
3. Recursive Patterns Open Language Issues Open LDM Issues in Pattern-Matching (v2) #2095

[Joe4evr]

Warnings for non-nullable fields that are not explicitly initialized

Glad this was considered, albeit with the conclusion of not doing anything (for now). Guess the best option for the dev is proper documentation that explains when what fields are/aren't null, and to explicitly surpress the warning by way of:

public SomeClass Foo { get; private set; } = null!;

[agocke]

@Joe4evr Right, our guidance right now is to initialize with = null!;