LogEventInfo constructor with eventProperties as IReadOnlyList #4628
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
snakefoot
force-pushed
the
logevent-properties-init
branch
2 times, most recently
from
46faa01 to
0c13d2b
Compare
snakefoot
force-pushed
the
logevent-properties-init
branch
from
0c13d2b to
e3f64ed
Compare
|
Kudos, SonarCloud Quality Gate passed! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allow users to create LogEventInfo where Properties-dictionary is created with required capacity.
Have use-case where application wants to capture lots of context-properties, for later output in json-file. Instead of adding the properties one-by-one with dictionary-resize, then this will reduce memory-allocation.