Skip to content

Conversation

@jjonescz
Copy link
Member

@jjonescz jjonescz commented May 13, 2025

Fixes #11718.

Review commit-by-commit to see codegen diff.

@jjonescz jjonescz marked this pull request as ready for review May 13, 2025 13:30
@jjonescz jjonescz requested review from a team as code owners May 13, 2025 13:30
@jaredpar jaredpar requested a review from 333fred May 13, 2025 16:46
}

// Collect attributes that should be propagated to the type inference method.
var withAttributes = StringBuilderPool.GetPooledObject();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason not to use the standard using pattern for pooled objects? After all, that's the pattern used in the code above for metadataPairs and would avoid all of the extra accesses for Object below.

using var _ = StringBuilderPool.GetPooledObject(out var withAtttributes);

@jjonescz
Copy link
Member Author

@333fred @DustinCampbell @dotnet/razor-compiler for a second review, thanks

@jjonescz jjonescz merged commit 013cbf5 into dotnet:main May 17, 2025
11 checks passed
@jjonescz jjonescz deleted the 11718-DynamicallyAccessedMembers branch May 17, 2025 08:32
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone May 17, 2025
@RikkiGibson RikkiGibson modified the milestones: Next, 18.0 P1 Aug 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

InputBase<TValue> produces trim warnings IL2091 for built in types

5 participants