Kenneth Hoff
Kenneth Hoff
> We are in the process of converting a huge MVC application from 4.8 to NET8 "Oh, how big are we talking?" > It currently has 7653 controllers "Oh, that's...
> Does it make sense to extend this to strings? Imagine that you defined next > [...] Literal types are something else entirely that I'd love to have but feels...
>as suggested by @colinhacks 😢 (Although, I guess he did suggest it, I just created the issue about the general idea )
This feels relevant to this conversation: https://github.com/dotnet/extensions/discussions/4735
I'm assuming this will be looked at in conjunction with the compiler rewrite that's underway? (At least the foundations for supporting it so that it can be supported quickly thereafter)
@marchy could this workaround be improved by this suggestion? Allowing you simply write ```c# _ => Do({ // Logic }), ``` https://github.com/dotnet/csharplang/discussions/6122
Personally I swapped to Swashbuckle, and will swap over to the [built-in support](https://github.com/dotnet/aspnetcore/issues/54598) in .Net 9 as soon as possible.
This is blocking me from using NSwag currently, so I had to temporarily revert to Swashbuckle despite that not having a commit in almost a year.
I'd like to see some way of calling the constructor of a type and/or setting some property during initialization. The first thing that came to mind is the comparer of...
> `[1, 2, 3].Select(i => i.ToString()).ToArray()` I assume you could also do this? ```c# [ ..[1, 2, 3].Select(i => i.ToString()) ] ```