You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TorchFix should understand statically types of the objects. This feature will enable more rules and more precise targeting for the existing rules. The implementation will require adoption of Pyre and LibCST’s TypeInferenceProvider. The feature will likely be optional as running Pyre may be a barrier for some users.
As an example, currently TorchFix will understand that this qr is a deprecated function here:
But not when using method notation - a.qr() - because TorchFix doesn't understand statically that a is a PyTorch tensor, maybe it's some unrelated object that just happens to have a method named qr.
The text was updated successfully, but these errors were encountered:
TorchFix should understand statically types of the objects. This feature will enable more rules and more precise targeting for the existing rules. The implementation will require adoption of Pyre and LibCST’s
TypeInferenceProvider
. The feature will likely be optional as running Pyre may be a barrier for some users.As an example, currently TorchFix will understand that this
qr
is a deprecated function here:But not when using method notation -
a.qr()
- because TorchFix doesn't understand statically thata
is a PyTorch tensor, maybe it's some unrelated object that just happens to have a method namedqr
.The text was updated successfully, but these errors were encountered: