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

Minor formatting issue on "<no attribute>" case

Browse source
This commit is contained in:
Julien Couvreur 2018-07-19 07:26:34 -07:00 committed by GitHub
parent 1b4d4e5e7c
commit 9b4e7a8c62
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
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/2018/LDM-2018-07-16.md
View file

@ -117,7 +117,7 @@ Proposal:
* `[NonNullTypes(true)]`: Warnings are on and unannotated types are non-nullable
* `[NonNullTypes(false)]`: Warnings are on but unannotated types are oblivious
* <no attribute>: Warnings are off and unannotated types are oblivious
* `<no attribute>`: Warnings are off and unannotated types are oblivious
The biggest benefit: if the warning opt-in is in source code, the nullable
warnings are not a breaking change. It's also noted