about summary refs log tree commit diff
path: root/src/test/rustdoc-js-std/string-from_ut.js
diff options
context:
space:
mode:
authorRalf Jung <post@ralfj.de>2020-05-18 08:48:43 +0200
committerGitHub <noreply@github.com>2020-05-18 08:48:43 +0200
commit2a9066479859f4aa22a08c71cd03f9b06ec99b7c (patch)
tree6d0af71a057da2b3f23dc2a492fa782f8136a3ff /src/test/rustdoc-js-std/string-from_ut.js
parent35d86693acd1cabc61531d3daf24f49eb9404899 (diff)
parentaea0186fe5e583b101016e40da55bd9adcd0bc27 (diff)
downloadrust-2a9066479859f4aa22a08c71cd03f9b06ec99b7c.tar.gz
rust-2a9066479859f4aa22a08c71cd03f9b06ec99b7c.zip
Rollup merge of #72143 - rust-lang:steveklabnik-must-use, r=sfackler
make offset must_use

https://djugei.github.io/bad-at-unsafe/ describes an error a user had when trying to use offset:

> At first I just assumed that the .add() and .offset() methods on pointers would mutate the pointer. They do not. Instead they return a new pointer, which gets dropped silently if you don't use it. Unlike for example Result, which is must_use annotated.

This PR only adds `offset`, because I wanted to float the idea; I'm imagining that there's more than just `add` and `offset` that could use this. I am also very open to re-wording the warning.

r? @rust-lang/libs
Diffstat (limited to 'src/test/rustdoc-js-std/string-from_ut.js')
0 files changed, 0 insertions, 0 deletions