-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added IteratableGatherer for future zero alloc implementations. #927
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This helps to protect the addition and removal of whole MetricFamilies. But it doesn't protect editing existing MetricFamilies in place. For example, if your set of metrics is entirely static, you just want to change a value now and then by directly changing only the
Value
protobuf message deep down within a MetricFamily, you would still create data races with this approach.In other words, after
At()
is called, the iterator has no control over the usage of the returned MetricFamily anymore. You only moved the problem one level down (from the MetricFamily slice to an individual MetricFamily).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree, I plan to explicitly mention in the interface that after
Next
you lose control over memory space pointed by pointer. SeeGatherIterate
method comment. Also see implementation.I don't see any other type safe way to do it. Even my initial idea with
GatherForeach(f func(*dto.MetricFamily) error) error
has the same issue - someone might reuse it.We have to rely on runtime tests and interface comments, unfortunately. But this will work. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well - there is one type safe manner. We could tie gathering with encoding in some
GatherEncode(encoder) error
- but:But might be way to go