Skip to content
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

US-11: having both "bound" and "extent" is redundant #180

Closed
sdutoit opened this issue Sep 19, 2013 · 1 comment
Closed

US-11: having both "bound" and "extent" is redundant #180

sdutoit opened this issue Sep 19, 2013 · 1 comment
Labels
ballot-comment Response to an NB or ISO comment on a ballot big An issue causing a large set of changes, scattered across most of the text.

Comments

@sdutoit
Copy link
Contributor

sdutoit commented Sep 19, 2013

N3733 US-11 says:

Two distinct terms of art, bound and extent, are now used to denote an array’s number of elements. For both consistency and improved technical accuracy, a single term of art should be adopted and used throughout the standard.

It goes on to propose:

Because extent is the user-visible term used in the Library’s interface, its consistent use would avoid breaking existing programs. See the wording proposed in N3549.

@sdutoit
Copy link
Contributor Author

sdutoit commented Sep 24, 2013

This issue has been rejected by CWG.

@sdutoit sdutoit closed this as completed Sep 24, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ballot-comment Response to an NB or ISO comment on a ballot big An issue causing a large set of changes, scattered across most of the text.
Projects
None yet
Development

No branches or pull requests

1 participant