feat: optimize RestMethodInfo
, reduce dictionary allocations and li…
#1742
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.
ParameterInfoMap
toParameterInfoArray
.Headers
,HeaderParameterMap
,PropertyParameterMap
,QueryParameterMap
,AttachmentNameMap
to only allocate a dictionary when needed.Empty
dictionary is a little risky but I dont see why we'd ever want to mutate the collection.EmptyDictionary<TKey, TValue>.get()
to create static empty dictionaries. I would prefer to useImmutableDictionary.Empty
and changeDictionary
toIReadOnlyDictionary
but they aren't available in . Net Framework.bodyParamEnumerable
andauthorizeParamsEnumerable
now use a tuple instead of an anonymous class.HeaderCollectionParameterIndex
instead of the hashsetHeaderCollectionParameterMap
We could probably get away with using arrays instead of
Dictionary<int, TSomething>
they would use less memory in most cases and would have faster lookups for smaller numbers.Saves 4Kb of memory, I might be able to do more after profiling.
Original
Changes