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

Fix typos (#5210)

Browse source
This commit is contained in:
Joseph Musser 2021-09-21 12:53:30 -04:00 committed by GitHub
parent fab06e432c
commit 088f20b6f9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
meetings/2021/LDM-2021-09-15.md
View file

@ -47,7 +47,7 @@ https://github.com/dotnet/csharplang/issues/4018
We took a first pass over this proposal in the second half of the LDM. At first brush, there are a couple of major points of contention:
1. Should we allow redeclaration, or should we have some from of `into` pattern that would allow the reuse of an existing variable in
1. Should we allow redeclaration, or should we have some form of `into` pattern that would allow the reuse of an existing variable in
a pattern?
2. Is variable declaration across multiple expressions ok, or should it only be permissible within a single pattern?

2
meetings/2021/LDM-2021-09-20.md
View file

@ -29,7 +29,7 @@ https://github.com/dotnet/csharplang/discussions/5157
We have a number of reports from users who have been broken by changes in overload resolution, mostly because a set of overloads that
used to succeed in overload resolution are now ambiguous. A smaller group met to discuss a number of different potential solutions to
the issue. These options where:
the issue. These options were:
1. Leave the breaking changes as-is.
2. Change “method type inference” and “best common type” to not infer from the natural type of a lambda expression or method group.