-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
In JS interop, add Invoke/InvokeAsync overloads that use C#11 param span #40098
Comments
Thanks for contacting us. We're moving this issue to the |
Is this still part of the C# 11 / .NET 7 roadmap? Or will it be shipped later? Because I don't find params span here |
@mu88 It's still a .NET 7 candidate, however we haven't assigned it to a particular milestone as it's not clear we have capacity to do it. If you're interested in doing a PR for this, that might be what's needed to get it in on time. Otherwise I can't predict yet whether or not it will make it. |
@mu88 Oh actually I see your point that the language feature itself isn't there yet. In that case it's fairly clear that it wouldn't be something we could do for Blazor! |
Yeah that's what I mean @SteveSandersonMS - I'm happy to assist as soon as the language feature is available |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
Is there an approved API proposal? |
It looks like this C# language feature was original proposed on this Issue: dotnet/csharplang#1757 |
Hopefully we can save one allocation per call, at least in the cases that had to use
params
in the past.The text was updated successfully, but these errors were encountered: