Encourage using raw strings in registry docs #3847
Merged
+2
−2
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 is a bit of a nitpick on how to write strings when they contain Windows-like paths. Generally, I think that raw strings are preferable in this scenario because
cmd.exe).\instead of\\. I think that characters like newlines (\n), tabs (\t), etc. are rare enough in paths that this is a reasonable trade-off.I noticed a lot of other places where there were strings with
\\that could be converted to raw strings. If this stylistic change makes sense, I can convert all of those if wanted. Right now I was just focusing on the documentation that I was reading.