Use compiler-generated delegate caches in ToDelimitedString
#966
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.
This PR removes all
StringBuilderAppenders
members that were designed to serve as static caches of delegates for use inToDelimitedString
implementations. This may have been significant in the past, but now using a simple static lambda seems to be simpler and the compiler-generated cached delegate run faster. It does however come at the cost of an additional allocation because while the lambdas themselves are static, the delegate caching gets hosted into a non-static class (<>c
below) generated by the C# compiler and the bodies converted into regular instance-based methods:Per dotnet/roslyn#51344, this is done so because:
In the StackOverflow question “Delegate caching behavior changes in Roslyn”, @Pilchie also notes in a comment:
Benchmarks seem to agree:
StaticLambda
StaticMethodGroup
StaticLocalFunction
CustomCachedDelegate
StringBuilderAppenders.zip
UserQuery-20230218-113452.log.txt