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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<valarray>: Implement copies for slice_array, gslice_array, mask_array, and indirect_array #988
<valarray>: Implement copies for slice_array, gslice_array, mask_array, and indirect_array #988
Changes from all commits
e00b11a
563960d
a445153
e10ba6a
7c1ef11
8c97417
974ccb2
b776945
7d4b040
e4afd4b
ae46fb4
662fbe9
dd3d547
243bb3a
5e7a331
8b84713
c5a2ba7
8c251df
471720c
caf1fc0
1a12d38
454246e
11e1412
2a6a122
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No change requested, just a stylistic comment - while we have tests that vary in their usage of
using namespace std;
and it's fine tostd::
qualify everything, even when the namespace prevents ambiguity I think that naming things identically to Standard identifiers makes things unnecessarily hard to read/search. (Being able to search for all occurrences ofslice_array
in product and test code, and having few spurious results show up, is useful.) Any other names would be fine; e.g.slice_array_copy
won't show up in a whole-word search.Since it looks like this PR will be ready to merge with a couple of include fixups (yay!), I don't think it's worth renaming now, but I wanted to mention it.