Created on 2017-02-03.00:00:00 last changed 90 months ago
[ 2017-07 Toronto Thurs Issue Prioritization ]
This is not a defect, but a feature request (and a large one). Papers welcome, but closing as NAD
Most implementations have poor testing and support for instantiating standard library templates with volatile-qualified types. We should grant a library-freedom to conforming implementations so that support for volatile (and const volatile) qualified types in standard library templates is not required unless explicitly specified — and mandate such support for all templates in the <type_traits> header. Additional support is already specified in most places we would be interested (e.g., tuple API). We may want to additionally guarantee support through forwarding references.
Proposed change: add a new 17.6.5.x Volatile Qualified Types [res.on.volatile.type] describing the intended level of support for volatile qualifiers.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-07-15 23:15:19 | admin | set | messages: + msg9390 |
| 2017-07-15 23:15:19 | admin | set | status: new -> nad |
| 2017-02-03 00:00:00 | admin | create | |