Skip to content

BitScanForward clarification to avoid ambiguous "return" term. #4378

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

Merged

Conversation

mstrgram
Copy link
Contributor

The remarks section has been reworded to avoid confusing use of the word "return" for both actual return value and the bit index written to the address given in the first parameter.

@prmerger-automator
Copy link
Contributor

@mstrgram : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 7a953f7:

✅ Validation status: passed

File Status Preview URL Details
docs/intrinsics/bitscanforward-bitscanforward64.md ✅Succeeded

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

Copy link
Contributor

@colin-home colin-home left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mstrgram Thanks for the clarification.

@colin-home colin-home merged commit 3e3a002 into MicrosoftDocs:main Jan 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants