Rename SafeValue to ToStringValue #13376
Merged
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.
Following up on the changes I made in #13367, @gaearon suggest that "safe" could be read as necessary for security. To avoid misleading future readers, I'm changing the name.
A few names where discussed in the previous PR. I think
ToStringValue
makes sense since the value itself is not a string yet but an opaque type that can be cast to a string. For the actual string concatenation, I've usedtoString
now to avoid confusion.toStringValueToString
is super weird and the function is namespaced anyway.Definitely open for other suggestions here as well. My plan is to wait until we wrap up #13362 and then rebase afterwards.