Amortise HTTP Result Content-Type arrays #56525
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Amortise Content-Type arrays
Amortise the
Content-Typearrays used for HTTP result endpoint metadata.Description
TypedResults' metadata.ProducesResponseTypeMetadata.CreateUnvalidated()to bypassContent-Typevalidation for these static values. If theInternalsVisibleTois undesirable, this could be reverted but this would need the re-used content-types to astring[], which then means they could in theory be edited at runtime via a cast as the compiler generated<>z__ReadOnlyArray`1type would no longer be used for the collection expression.application/octet-stream.The changes resolve a number of
CA1861,IDE0028andIDE0300analyser suggestions.The theory is that the re-use of the arrays and ability to bypass the
Content-Typevalidation will reduce the an application's memory usage and speed up the population of endpoint metadata.