maxmustermann/csharplang
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix typo.

Browse source
This commit is contained in:
Fredric Silberberg 2021-04-16 11:28:16 -07:00
parent f894bac818
commit d8430957be
No known key found for this signature in database
GPG key ID: BB6144C8A0CEC8EE
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
meetings/2021/LDM-2021-04-14.md
View file

@ -51,7 +51,7 @@ few alternate syntaxes to see if we could avoid the need to make `field` a conte
compiler work, our ultimate conclusion here is that we'd prefer to do the work needed to make `field` a contextual keyword over taking what we
feel is an inferior syntax. As part of this work, we can consider making the public Roslyn APIs around backing fields more consistent. Today,
there are differences between what `GetMembers()` will return for auto-properties vs field-like events, and in order to implement the `field`
keyword we will likely need to take the same strategy as we did with field-like events to avoid circularties. We will also consider standardizing
keyword we will likely need to take the same strategy as we did with field-like events to avoid circularities. We will also consider standardizing
the behavior here as it has also been a source of Roslyn-API consumer confusion in the past. We will also consider a .NET 6 warning wave to prefix
`field` identifiers in properties that do not correspond to a backing field with either `@` or `this.`, as appropriate.