-
Notifications
You must be signed in to change notification settings - Fork 706
Make EValue template constructor MSVC friendly #6631
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/6631
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New FailureAs of commit 9fa66ad with merge base 8a4e492 ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
This pull request was exported from Phabricator. Differential Revision: D65402442 |
Summary: The current EValue template constructor is not MSVC friendly, in order to make it MSVC friendly had to make some small changes such as: - Using a default template argument (typename = typename std::enable_if<...>::type). This means that the std::enable_if condition is evaluated when the template is instantiated. - Separating the SFINAE condition from the function signature. Reviewed By: dbort Differential Revision: D65402442
b4aed27 to
d2ff69d
Compare
|
This pull request was exported from Phabricator. Differential Revision: D65402442 |
Summary: The current EValue template constructor is not MSVC friendly, in order to make it MSVC friendly had to make some small changes such as: - Using a default template argument (typename = typename std::enable_if<...>::type). This means that the std::enable_if condition is evaluated when the template is instantiated. - Separating the SFINAE condition from the function signature. Reviewed By: dbort Differential Revision: D65402442
d2ff69d to
8ece7b7
Compare
|
This pull request was exported from Phabricator. Differential Revision: D65402442 |
Summary: The current EValue template constructor is not MSVC friendly, in order to make it MSVC friendly had to make some small changes such as: - Using a default template argument (typename = typename std::enable_if<...>::type). This means that the std::enable_if condition is evaluated when the template is instantiated. - Separating the SFINAE condition from the function signature. Reviewed By: dbort Differential Revision: D65402442
8ece7b7 to
cfba69f
Compare
|
This pull request was exported from Phabricator. Differential Revision: D65402442 |
Summary: The current EValue template constructor is not MSVC friendly, in order to make it MSVC friendly had to make some small changes such as: - Using a default template argument (typename = typename std::enable_if<...>::type). This means that the std::enable_if condition is evaluated when the template is instantiated. - Separating the SFINAE condition from the function signature. Reviewed By: dbort Differential Revision: D65402442
cfba69f to
d97a89d
Compare
|
This pull request was exported from Phabricator. Differential Revision: D65402442 |
Summary: The current EValue template constructor is not MSVC friendly, in order to make it MSVC friendly had to make some small changes such as: - Using a default template argument (typename = typename std::enable_if<...>::type). This means that the std::enable_if condition is evaluated when the template is instantiated. - Separating the SFINAE condition from the function signature. Reviewed By: dbort Differential Revision: D65402442
d97a89d to
8569574
Compare
|
This pull request was exported from Phabricator. Differential Revision: D65402442 |
Summary: The current EValue template constructor is not MSVC friendly, in order to make it MSVC friendly had to make some small changes such as: - Using a default template argument (typename = typename std::enable_if<...>::type). This means that the std::enable_if condition is evaluated when the template is instantiated. - Separating the SFINAE condition from the function signature. Reviewed By: dbort Differential Revision: D65402442
8569574 to
a411fef
Compare
|
This pull request was exported from Phabricator. Differential Revision: D65402442 |
Summary: The current EValue template constructor is not MSVC friendly, in order to make it MSVC friendly had to make some small changes such as: - Using a default template argument (typename = typename std::enable_if<...>::type). This means that the std::enable_if condition is evaluated when the template is instantiated. - Separating the SFINAE condition from the function signature. Reviewed By: dbort Differential Revision: D65402442
a411fef to
1403a49
Compare
|
This pull request was exported from Phabricator. Differential Revision: D65402442 |
Summary: The current EValue template constructor is not MSVC friendly, in order to make it MSVC friendly had to make some small changes such as: - Using a default template argument (typename = typename std::enable_if<...>::type). This means that the std::enable_if condition is evaluated when the template is instantiated. - Separating the SFINAE condition from the function signature. Reviewed By: dbort Differential Revision: D65402442
1403a49 to
9fa66ad
Compare
|
This pull request was exported from Phabricator. Differential Revision: D65402442 |
Differential Revision: D65402442