-
Notifications
You must be signed in to change notification settings - Fork 720
Use std::optional #12707
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
Use std::optional #12707
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12707
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 1 New Failure, 3 Unrelated FailuresAs of commit df13091 with merge base 892d40e ( NEW FAILURE - The following job has failed:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
BROKEN TRUNK - The following jobs failed but was present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@manuelcandales I have fixed the build errors. |
|
@JacobSzwejbka Fixed |
|
the optional classes being replaced here are already synonymous with std::optional and therefore this is a cosmetic change, right? If so, with the 1.0 branch cut looming, let's hold off on merging this one. |
|
@swolchok Thank you for your kindly support. |
|
1.0 is safely out the door! mind knocking out a rebase? |
|
@swolchok Done |
swolchok
left a comment
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.
thanks! intend to merge when CI is green
|
@swolchok I need some iterations to fix CI errors. |
|
To add the ciflow label This helps ensure we don't trigger CI on this PR until it is actually authorized to do so. Please ping one of the reviewers if you do not have access to approve and run workflows. |
Signed-off-by: cyy <cyyever@outlook.com>
Signed-off-by: cyy <cyyever@outlook.com>
Signed-off-by: Yuanyuan Chen <cyyever@outlook.com>
Signed-off-by: Yuanyuan Chen <cyyever@outlook.com>
Signed-off-by: Yuanyuan Chen <cyyever@outlook.com>
|
@swolchok @shoumikhin The current CI failures are unrelated. |
Reverts #12707 This causes 1000s of internal CI failures, e.g., error: no template named 'optional' in namespace 'torch::executor'; did you mean simply 'optional'? using optional = torch::executor::optional<T>; ^~~~~~~~~~~~~~~~~~~~~~~~~ optional note: 'optional' declared here using ::executorch::aten::optional;
### Summary Move remaining usage of optional to `std::optional`. --------- Signed-off-by: cyy <cyyever@outlook.com> Signed-off-by: Yuanyuan Chen <cyyever@outlook.com>
Reverts pytorch#12707 This causes 1000s of internal CI failures, e.g., error: no template named 'optional' in namespace 'torch::executor'; did you mean simply 'optional'? using optional = torch::executor::optional<T>; ^~~~~~~~~~~~~~~~~~~~~~~~~ optional note: 'optional' declared here using ::executorch::aten::optional;
Summary
Move remaining usage of optional to
std::optional.