-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Rewrite sync::one::Once.doit #13351
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
Closed
Closed
Rewrite sync::one::Once.doit #13351
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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 hidden or 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 sort of optimization is possible in many other places throughout the rest of the codebase, and it generally seems like a bit of a premature optimization currently. I don't disagree that in theory this allows for more inlining and fewer calls, but I'd like to avoid this semi-obscure pattern throughout the codebase for now (until we see that it is indeed truly necessary).
Some other places where this pattern would be nice:
and many more I presume. For now, are you ok with just making this one method that's not marked
#[inline]
? I would imagine that super perf-sensitive contexts are using LTO anyway, but that may be wrong.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'm willing to change this back to one function, but I'd like to know if there's a better reason for doing so other than "this isn't a pattern we're using elsewhere at the moment". I don't think using this pattern here hurts comprehension for the reader.
The main reason I went ahead and did this is because I was trying to optimize for the already-finished case, as it can reasonably be expected that the vast majority of calls to
doit()
will be doing nothing.