about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc/example/example.rs
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2023-07-22 11:48:54 +0200
committerGitHub <noreply@github.com>2023-07-22 11:48:54 +0200
commit746d507c726dbbae0b3067925215c0aa57a93975 (patch)
treef6ea2cadfa6090ea375783778a5ea9a71ff87fed /compiler/rustc_codegen_gcc/example/example.rs
parent0877d11e8dee12839804909171e61ad77ae0656a (diff)
parent7d17a263d1a6e46700f65d378a9ae7280a2b3371 (diff)
downloadrust-746d507c726dbbae0b3067925215c0aa57a93975.tar.gz
rust-746d507c726dbbae0b3067925215c0aa57a93975.zip
Rollup merge of #113876 - darklyspaced:master, r=cuviper
fix docs & example for `std::os::unix::prelude::FileExt::write_at`

 Changelog:
 * used `File::create` instead of `File::read` to get a writeable file
 * explicity mentioned the bug with `pwrite64` in docs

Unfortunately, I don't think that there is really much we can do about this since the feature has already been stabilised.

We could potentially add a clippy lint warning people on Linux that using `write_at` with the `O_APPEND` flag does not exhibit the behaviour that they would have assumed.

fixes #113627
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/example.rs')
0 files changed, 0 insertions, 0 deletions