Renaming array_view and string_view, as per WG21 discussions. #166
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
neilmacintosh
pushed a commit
that referenced
this pull request
Nov 4, 2015
Renaming array_view and string_view, as per WG21 discussions.
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.
The Library Evolution Working Group of WG21 gave us helpful feedback at the Kona meeting regarding naming of array_view and string_view. The result of discussion was that
spanwas preferred forarray_viewandstring_spanforstring_view. Note there is an existingstring_viewin the Library Fundamentals TS and that waystring_spanwill not conflict with that type.This PR renames both types to follow this guidance.