Repository navigation
Remove redundant weight_dtype validation in MXDynamicActivationMXWeightConfig - #4991
bogoconic1 wants to merge 1 commit into
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/4991
Note: Links to docs will display an error until the docs builds have been completed. This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
Hi @bogoconic1! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
5671c5c to
86015bc
Compare
|
In my org we really dislike dead code, these days with AI its much easier to add something back when needed so there's every reason to be aggressive to remove anything unnecessary. But AI itself hates deleting code unless I tell it to |
Given
self.activation_dtype == self.weight_dtype, once we validateself.activation_dtypeits not necessary to validateself.weight_dtype. Unless I am missing something that the maintainers know 🤔