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
add fix for GCC. #40
add fix for GCC. #40
Conversation
I'm probably going to need a few days, unfortunately. Do you happen to know which version of GCC requires this? |
|
@dreiss - any updates on this? If there are things I can help with, I'm happy to. |
@dreiss Will you have any time to look at this in the next day or so? I was hoping to see Java bindings for Windows land in PyTorch 1.7.0, but this is now not possible since the 1.7.0 RC has already been cut. I'd still like to see it land ASAP and this is the last thing standing in the way. Since this is such a small PR, I'm hoping it can be imported into phabricator and land cleanly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dreiss has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
@erip has updated the pull request. You must reimport the pull request before landing. |
@dreiss thanks for making the required changes. Is there a reason my contributions are being committed directly to the repo instead of being merged? This is the second PR that's been ignored with nearly identical fixes being added directly to the repo. |
Motivation
Why are you making this change?
To fix build with GCC so PyTorch can build with newest commits.
Summary
Updates return type to be explicitly pinned within the class. SFINAE etc. etc.
How does the code work?
Why did you choose this approach?
https://stackoverflow.com/a/14419935/2883245
Test Plan
How did you test this change?
Any change that adds functionality should add a unit test as well.