Use #[inline] everywhere. #145
Merged
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
I tried to follow the following rules for determining if something
should be #[inline]:
- Functions that are trivial. (E.g. implementations of `Add`, or a
trivial `new` function.)
- Functions that do not appear trivial, but would generate trivial
assembly. (E.g. functions with mostly Rust code that don't result much
generated code: `use` statements, wrapping values, bit twiddling,
`#[cfg]`, `PhantomData`, etc.)
- Functions that only call another function.
- Functions that could benefit a lot from inline optimization:
- Functions that have asserts/matches/ifs on the parameters, which are
likely constant or known to be in a certain range:
If a function starts with `assert!(param < 32)`, inlining enables
the compiler to completely optimize the check away if it already
knows the value to always be less than 32.
If a function matches on a parameter, inlining allows throwing all
but one match arm away.
- Functions where knowing the return value could benefit optimization on
later calls/code.
phil-opp
reviewed
Apr 11, 2020
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.
I tried to follow the following rules for determining if something
should be #[inline]:
Add, or atrivial
newfunction.)assembly. (E.g. functions with mostly Rust code that don't result much
generated code:
usestatements, wrapping values, bit twiddling,#[cfg],PhantomData, etc.)likely constant or known to be in a certain range:
If a function starts with
assert!(param < 32), inlining enablesthe compiler to completely optimize the check away if it already
knows the value to always be less than 32.
If a function matches on a parameter, inlining allows throwing all
but one match arm away.
later calls/code.