The proper blending of typed union and descriminated union for C# would be amazing - that means C# developers will enjoy the both worlds of the union. 🎉
@@z0nx I approve this message. Ok, the people have spoken, get on it Microsoft. Good talk, good run csharp team, you can pack it in, we will functionally take it from here, kthxbai. lol. how I wish it were so.
I've been reading Mads' and other's works on the expression problem in the early 2000s. Looking forward to if you can make it in C# with the extensions. That would be awesome.
@@konstsh2240 that doesn't sound like something I'd want anyway. What do you mean exactly? That "firstname" or "firstName" won't match if the enum value is "FirstName"?
@@michaldivismusic For example when json field might have a fixed number of string values like "Reference::Point", "Reference::Edge", "Dimension::PointToPoint" and a number of others and you want to parse them into enum Annotation{REFERENCE_POINT, REFERENCE_EDGE, DIMENSION_POINT_TO_POINT} - the the real case of json response I'm dealing with on current project and turned I had to look for side package
20:50 sounds like a spooky action at a distance. I'd just make the default type an array or a list and call it a day. if you need something more specific, specify the type. if you don't, is an array. or a list.
Sorry Mads but what you showed there of 'Typescript' style unions made me throw up a little bit. We need real union types and better function type inference both on declaration and usage in C#.
@@GeorgeTsiros I have programmed quite a bit of both Pascal/Delphi and C# and I really can't see how what you are saying is true. The parallels between Java and C# are pretty obvious, while the similarities between Dephi and C# pretty much boil down to: both are imperative, both are OO. Which of course is true for most popular programming languages.
literally the point of the changes is to enable more scenarios for delight, though. What change were you forced to make that reduced that delight? What breaking change happened that affected you?
The proper blending of typed union and descriminated union for C# would be amazing - that means C# developers will enjoy the both worlds of the union. 🎉
I want union type to be first citizen. That is something I really love in TS
Explicit extensions are great but we need a way to explicitly implement interfaces or, ideally, traits. We are so close!
Mads seems like a very nice person to talk to!
Can't wait to work with C#13
I hope it's going to be available by then, not a lot of updates recently... fingers crossed!
Ah, this must be that "talk from yesterday"!
The most important change I want for csharp is likely not going to happen. I want full type inference. It would be so incredible.
cant we just replace chsarp with fsharp already
@@z0nx I approve this message. Ok, the people have spoken, get on it Microsoft. Good talk, good run csharp team, you can pack it in, we will functionally take it from here, kthxbai. lol. how I wish it were so.
I've been reading Mads' and other's works on the expression problem in the early 2000s. Looking forward to if you can make it in C# with the extensions. That would be awesome.
how about finally making enums convertable to json as strings out of the box?
a) It is not a language, but rather a BCL feature
b) It is already implemented, search for JsonStringEnumConverter
System.Text.Json has a built-in converter for that. It's just not the default.
@@michaldivismusic but it doesn't convert to string that doesn't match the enum property spelling
@@konstsh2240 that doesn't sound like something I'd want anyway. What do you mean exactly? That "firstname" or "firstName" won't match if the enum value is "FirstName"?
@@michaldivismusic For example when json field might have a fixed number of string values like "Reference::Point", "Reference::Edge", "Dimension::PointToPoint" and a number of others and you want to parse them into enum Annotation{REFERENCE_POINT, REFERENCE_EDGE, DIMENSION_POINT_TO_POINT} - the the real case of json response I'm dealing with on current project and turned I had to look for side package
20:50 sounds like a spooky action at a distance. I'd just make the default type an array or a list and call it a day. if you need something more specific, specify the type. if you don't, is an array. or a list.
Implementing interfaces on behalf of another type. A lot of pitfalls with this, but it would basically work like type classes which are fantastic
Great language ... thanks!
Aspnetcore results feels pretty hacky. A proper union type would be nice.
Is there a reason other than convention that C# is mostly double-spaced?
[ ] >> { } for collection expressions! Coming from an #fsharper :)
Yeah... we're not getting type classes, are we?
Sorry Mads but what you showed there of 'Typescript' style unions made me throw up a little bit. We need real union types and better function type inference both on declaration and usage in C#.
Its so funny how he goes out of his way not to say the word "Java" when talking about the initial design of C#
That's because C# is Pascal's/Delphi's grandchild, not Java's.
@@GeorgeTsiros I have programmed quite a bit of both Pascal/Delphi and C# and I really can't see how what you are saying is true. The parallels between Java and C# are pretty obvious, while the similarities between Dephi and C# pretty much boil down to: both are imperative, both are OO. Which of course is true for most popular programming languages.
@@Avantarius For starters, check out who _designed_ C#
"C# should be delightful" - this is why I love(d) it but I am not sure any more with the plethora of questionable features being added
literally the point of the changes is to enable more scenarios for delight, though. What change were you forced to make that reduced that delight? What breaking change happened that affected you?
всякой хернёй занимаются. лучше бы скорость и IL2CPP улучшали. меньше кучь, больше стеков.
what to do when u have not much to say…. ramble ramble ramble