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

Fix type for "whole" (#1337)

Browse source
This commit is contained in:
Unknown6656 2018-02-26 21:39:07 +01:00 committed by Julien Couvreur
parent b650b02f3d
commit cc23b5f6bd
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/2017/LDM-2017-10-11.md
View file

@ -127,7 +127,7 @@ This is probably right. We'll think about this more, but let's go with covarianc
# Null warnings
Feedback: Fine to warn in most places where a null value is given a nonnullable type, but we should beware of a "sea of warnings" effect. Specifically, we shouldn't warn on array creation, as in `new string[10]`, even though it creates a hole array of undesired nulls, because it is so common in current code, and couldn't have been done "safely" before.
Feedback: Fine to warn in most places where a null value is given a nonnullable type, but we should beware of a "sea of warnings" effect. Specifically, we shouldn't warn on array creation, as in `new string[10]`, even though it creates a whole array of undesired nulls, because it is so common in current code, and couldn't have been done "safely" before.
## Conclusion