do not specialze for abstract_eval_nonlinearized_foreigncall_name#59722
Merged
do not specialze for abstract_eval_nonlinearized_foreigncall_name#59722
abstract_eval_nonlinearized_foreigncall_name#59722Conversation
Since `e` is potentially arbitrary runtime value, we should not specialize on it.
Member
|
Sure. This hack is slated for imminent deletion though, since these hacks are not relevant after #59165 (just waiting for a new LinearSolve release now). |
Member
Author
|
Ok. Given that the branch won't be backported to 1.12, I believe this should be backported to make inference on 1.12 slightly better. |
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Following up #58872.
Since
eis potentially arbitrary runtime value, we should not specialize on it.