[multifn] Optimize non-cached effective-dispatch-value #155
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.
Further improvements to method dispatching machinery. When it is cached, this shouldn't matter, but I keep encountering cases where it is not cached and thus it matters a bit.
For the benchmark, I've accumulated a sample of ~20k argument sets to
effective-dispatch-valueI got these results:Normalized to a single invocation, this means that a single invocation allocations dropped from
1.39KBto380Bwhich looks significant enough for something as basic as a multimethod invocation.