Add macros for creating null-terminated string literals #1891
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kennykerr
changed the title
rylev
reviewed
Jul 12, 2022
rylev
previously approved these changes
Jul 12, 2022
This was referenced Jul 12, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update adds simple
s!andw!macros that produce null terminated UTF8 and UTF16 string literals that supports both Win32 and WinRT APIs. This is quite convenient as Rust does not provide null terminated string literals nor does it provide UTF16 literals. The resulting expressions point toconstdata that is both folded by the compiler and stored in constant pages.Fixes #484
Fixes #581