-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
optimize invokelatest #38835
Merged
Merged
optimize invokelatest #38835
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
vtjnash
force-pushed
the
jn/invokelatest-faster
branch
from
December 11, 2020 16:30
3ccf6aa
to
516fe7c
Compare
JeffBezanson
approved these changes
Dec 11, 2020
vtjnash
force-pushed
the
jn/invokelatest-faster
branch
from
December 11, 2020 17:06
516fe7c
to
3870a65
Compare
People previously were making dumb work-arounds like try/catch around this to get a bit faster here, since the compiler couldn't optimize it before. Applications typically shouldn't use this function in performance sensitive places, as it hints that their design is flawed, but might as well make it faster anyways. and optimize invokelatest kwcall too, while we are at it
vtjnash
force-pushed
the
jn/invokelatest-faster
branch
from
December 11, 2020 19:40
3870a65
to
8b7f947
Compare
Keno
approved these changes
Dec 12, 2020
aviatesk
added a commit
to aviatesk/JuliaInterpreter.jl
that referenced
this pull request
Dec 15, 2020
this essentially updates to JuliaLang/julia#38835, where `_apply_latest` is renamed to `_call_latest`
simeonschaub
pushed a commit
to simeonschaub/JuliaInterpreter.jl
that referenced
this pull request
Dec 17, 2020
this essentially updates to JuliaLang/julia#38835, where `_apply_latest` is renamed to `_call_latest`
simeonschaub
pushed a commit
to simeonschaub/JuliaInterpreter.jl
that referenced
this pull request
Dec 17, 2020
this essentially updates to JuliaLang/julia#38835, where `_apply_latest` is renamed to `_call_latest`
vtjnash
added a commit
that referenced
this pull request
Feb 16, 2021
Applications typically shouldn't use this function in performance sensitive places, as it hints that their design is flawed, but might as well make it faster anyways. and optimize invokelatest kwcall too, while we are at it (cherry picked from commit 2ff110b)
ElOceanografo
pushed a commit
to ElOceanografo/julia
that referenced
this pull request
May 4, 2021
Applications typically shouldn't use this function in performance sensitive places, as it hints that their design is flawed, but might as well make it faster anyways. and optimize invokelatest kwcall too, while we are at it
staticfloat
pushed a commit
that referenced
this pull request
Dec 23, 2022
Applications typically shouldn't use this function in performance sensitive places, as it hints that their design is flawed, but might as well make it faster anyways. and optimize invokelatest kwcall too, while we are at it (cherry picked from commit 2ff110b)
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.
People previously were making dumb work-arounds like try/catch around this to get a bit faster here (which is slightly slower than a generic dispatch currently, so that "optimization" may actually directly reduce their performance), since the compiler couldn't optimize it before at all. Applications typically shouldn't use this function in performance sensitive places, as it hints that their design is flawed, but might as well make it faster anyways. There's not a lot of headroom for better performance, so I am skeptical of their performance analysis though.