this post was submitted on 20 Oct 2023
39 points (93.3% liked)
Programming
17406 readers
94 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The new list initializing syntax is less boilerplate, no?
Look how clunky it is to add support on a collection. Take the example here:
https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/operators/collection-expressions#collection-builder
It involves adding a new builder class, and they actually have to reference the function by string name.
It's actually making me even more angry now that I look at it in detail.
This is true of a lot of the opt-in language features though, isn't it? For example, you can just make an
.Addmethod on anyIEnumerabletype and get collection initializer syntax supported for it, even as an extension method. The same works forDisposeon ref structs I believe, and I remember there being a few other places where this was true (GetAwaiterI think?).This is for custom collections, right? And you don't even have to use it, you can keep using existing ctors for your custom collections
Worse case scenario you keep doing what we've always had to do. But for the 99% of use cases we get a much more streamlined initializer, with extensions to use our own.
I don't see how that's a bad thing