This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of Resolved status.

### 825. Missing rvalues reference stream insert/extract operators?

Section: 19.5.4.1 [syserr.errcode.overview], 20.3.2.2.12 [util.smartptr.shared.io], 99 [facets.examples], 22.9.4 [bitset.operators], 28.4.6 [complex.ops], 31.6 [stream.buffers], 32.8 [re.submatch] Status: Resolved Submitter: Alisdair Meredith Opened: 2008-04-10 Last modified: 2017-03-21

Priority: Not Prioritized

View all other issues in [syserr.errcode.overview].

View all issues with Resolved status.

Discussion:

Addresses UK 220

Should the following use rvalues references to stream in insert/extract operators?

- 19.5.4.1 [syserr.errcode.overview]
- 20.3.2.2.12 [util.smartptr.shared.io]
- 99 [facets.examples]
- 22.9.4 [bitset.operators]
- 28.4.6 [complex.ops]
- Doubled signatures in 31.6 [stream.buffers] for character inserters (ref 31.7.6.3.4 [ostream.inserters.character]) + definition 31.7.6.3.4 [ostream.inserters.character]
- 32.8 [re.submatch]

[ Sophia Antipolis ]

> Agree with the idea in the issue, Alisdair to provide wording.

[ Daniel adds 2009-02-14: ]

> The proposal given in the paper N2831 apparently resolves this issue.

[ Batavia (2009-05): ]

> The cited paper is an earlier version of N2844, which changed the rvalue reference binding rules. That paper includes generic templates `operator<<` and `operator>>` that adapt rvalue streams.

> We therefore agree with Daniel's observation. Move to NAD Editorial Resolved.

Proposed resolution: