-
Notifications
You must be signed in to change notification settings - Fork 967
Fix documentation of /DEBUG:FASTLINK and plain /DEBUG. #4783
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
@davidmatson : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Learn Build status updates of commit 27fc9f5: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
#label:"aq-pr-triaged" |
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.
Could you update the date metadata at the top of the file?
This is a meaningful change so we should update the date to reflect that it's the latest info.
This is a welcome update - thank you.
I assume that's just the ms.date? If so, done. (If not, please let me know the right way.) |
Learn Build status updates of commit c24954f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Perfecto. Thank you, @davidmatson |
From discussion with the product team, /DEBUG means the same thing as /DEBUG:FULL. This has been the case for the linker itself since at least VS 2013 and is currently the case with all templates. Remove statements that indicated /DEBUG sometimes meant /DEBUG:FASTLINK.
Also, recommend not using /DEBUG:FASTLINK, per the product team.