diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-07-30 20:36:33 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-07-30 20:36:33 +0200 |
| commit | 27e3a740ae28ed0d8ad27b617337cf4bfc6291d2 (patch) | |
| tree | e3dc888b3de402294d5153fe5464c6ebb4a7917f /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 89acdae9f243da15549c7a8bc737e6240c301790 (diff) | |
| parent | 79a22f4954704d65f8356be59c3d07851e31f074 (diff) | |
| download | rust-27e3a740ae28ed0d8ad27b617337cf4bfc6291d2.tar.gz rust-27e3a740ae28ed0d8ad27b617337cf4bfc6291d2.zip | |
Rollup merge of #98154 - vidhanio:master, r=workingjubilee
merge functionality of `io::Sink` into `io::Empty` Many times, there is a need for a simple dummy `io::Read`er + `io::Write`r, but currently the only options are `io::Empty` and `io::Sink` respectively. Having both of their functionality together requires writing your own boilerplate for something that makes sense to have in the standard library. This PR adds the functionality of `io::Sink` to `io::Empty`, making `io::Empty` be able to perform the tasks of both of the previous structs. (This idea was first mentioned in #24235) Note: I also updated some doc comments in `io::utils` in this pull request to fix inconsistencies between `io::Sink` and `io::Empty`. API Change Proposal: https://github.com/rust-lang/libs-team/issues/49
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions