Skip to content
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

Update C++ standard to C++17 #7464

Merged
merged 1 commit into from
Mar 24, 2023
Merged

Update C++ standard to C++17 #7464

merged 1 commit into from
Mar 24, 2023

Conversation

malfet
Copy link
Contributor

@malfet malfet commented Mar 24, 2023

To match C++ standard in PyTorch core

To match C++ standard in PyTorch core
@pytorch-bot
Copy link

pytorch-bot bot commented Mar 24, 2023

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/7464

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.

@malfet malfet merged commit d4adf08 into main Mar 24, 2023
@github-actions
Copy link

Hey @malfet!

You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py

@malfet malfet deleted the malfet-patch-1 branch March 24, 2023 23:17
@NicolasHug NicolasHug added code quality other if you have no clue or if you will manually handle the PR in the release notes labels Mar 27, 2023
facebook-github-bot pushed a commit that referenced this pull request May 15, 2023
Summary:
This diff should not be synced back to GH (no need, it's already there). I'm adding the [fbsync] prefix manually.

This is a manual sync of #7464 which was previously missed due to conflicts with D44192139.

Reviewed By: vmoens

Differential Revision: D45477018

fbshipit-source-id: da50b1f5804bab472d2c668c0303f344f696a1af
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla signed code quality other if you have no clue or if you will manually handle the PR in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants