Skip to content
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

Remove .Any lambda per call allocation from DefaultProblemDetailsWriter #43046

Closed
brunolins16 opened this issue Aug 2, 2022 · 0 comments · Fixed by #43055
Closed

Remove .Any lambda per call allocation from DefaultProblemDetailsWriter #43046

brunolins16 opened this issue Aug 2, 2022 · 0 comments · Fixed by #43055
Assignees
Labels
area-web-frameworks *DEPRECATED* This label is deprecated in favor of the area-mvc and area-minimal labels bug This issue describes a behavior which is not expected - a bug.
Milestone

Comments

@brunolins16
Copy link
Member

This lambda probably allocates per call, we should hand write .Any

Originally posted by @BrennanConroy in #42384 (comment)

@brunolins16 brunolins16 self-assigned this Aug 2, 2022
@brunolins16 brunolins16 added the area-web-frameworks *DEPRECATED* This label is deprecated in favor of the area-mvc and area-minimal labels label Aug 2, 2022
@brunolins16 brunolins16 added this to the 7.0-rc2 milestone Aug 2, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Sep 2, 2022
@danroth27 danroth27 added the bug This issue describes a behavior which is not expected - a bug. label Oct 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-web-frameworks *DEPRECATED* This label is deprecated in favor of the area-mvc and area-minimal labels bug This issue describes a behavior which is not expected - a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants