-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C# Design Notes for May 25, 2015 #3912
Comments
This was referenced Jul 12, 2015
Design notes have been archived at https://github.com/dotnet/roslyn/blob/future/docs/designNotes/2015-05-25%20C%23%20Design%20Meeting.md but discussion can continue here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
C# Design Meeting Notes for May 25, 2015
Agenda
Today we went through a bunch of the proposals on GitHub and triaged them for our list of features in issue #2136. Due to the vastness of the list, we needed to use some criterion to sort by, and though far from ideal we ordered them by number of comments, most to least.
Here's where we landed, skipping things that were already "Strong interest". Some are further elaborated in sections below.
vararg
calling convention in C# #37)Params IEnumerable
This needs more thinking - let's not just implement the straightforward design. There are perf issues, for instance, around implementing through the
IEnumerable<T>
interface instead of arrays directly.More type inference
Not a coherent proposal. But even if there was one, we probably wouldn't want it in C#.
Implicitly typed lambdas
These are mostly subsumed by local functions, which we'd rather do. It has some individual usefulness but not much synergy.
Object initializers for immutable objects
We want to think this together with withers, not sure what form it would take.
first item in loops is special
We recognize the scenario but it's not worthy of a feature.
vararg calling convention
Roll it in with params IEnumerable discussion for investigation.
XML literals
Never! We won't bake in a specific format.
The text was updated successfully, but these errors were encountered: