function signature for the "^" operator for strings #46884
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.
The returned value of this function should be shown so as to clear ambiguities on some scenarios.
As an example, it doesn't matter if the string is of length
0
or1
, the returned value will always be a string. This isn't intuitive to think of as first glance:Since it's said no where for the function to always return a string, its best to be in the function signature. And this will clear the ambiguities as pointed above.
A great example of this is in the
*
operator for strings and regex:As seen above, the
^
operator should follow the same standard too!I opened #46885 on the regex part as well, so its balanced.