This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 117b. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.
2025-08-11
2506. Structured bindings and array cv-qualifiersSection: 9.7 [dcl.struct.bind] Status: CD6 Submitter: Barry Revzin Date: 2018-12-11[Accepted at the February, 2022 meeting.]
According to 9.7 [dcl.struct.bind] paragraph 1,
A structured binding declaration introduces the identifiers v0, v1, v2, ... of the identifier-list as names of structured bindings. Let cv denote the cv-qualifiers in the decl-specifier-seq and S consist of the storage-class-specifiers of the decl-specifier-seq (if any). A cv that includes volatile is deprecated; see D.4 [depr.volatile.type]. First, a variable with a unique name e is introduced. If the assignment-expression in the initializer has array type A and no ref-qualifier is present, e is defined by
attribute-specifier-seqopt S cv A e ;
and each element is copy-initialized or direct-initialized from the corresponding element of the assignment-expression as specified by the form of the initializer.
This means that in an example like
const int arr[1]{};
auto [i] = arr;
i is a reference to const int. Presumably the fact that the array is copied should drop the array's cv-qualification.
Proposed resolution (December, 2021):
Change 9.7 [dcl.struct.bind] paragraph 1 as follows:
If the assignment-expression in the initializer has array type cv1A and no ref-qualifier is present, e is defined by...
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4