use ternery instead of ifelse
since ifelse force evaluation of the RHS
#78
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.
Made on top of #77 to avoid some merge conflicts and have up to date benchmarks.
I was looking at why the following benchmark allocates:
With the following PR we instead get
The benchmark in #75
goes from
to
Not a huge speedup but quite a big reduction in allocations which might be useful as other things improve.
I am not 100% sure why this is needed but I typically find the compiler optimizes better with ternary
?
overifelse
.