about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
diff options
context:
space:
mode:
authorYuki Okushi <jtitor@2k36.org>2021-04-04 00:19:37 +0900
committerGitHub <noreply@github.com>2021-04-04 00:19:37 +0900
commit961fa632d678362b303678e6b36b93764fd63322 (patch)
tree8c319acd07038c423d6801610009070424026c06 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
parent0daec04d657141e2eb2cea1675dd3e44624a8671 (diff)
parent5547d927467ef3398c3f509f0212ba26645a18da (diff)
downloadrust-961fa632d678362b303678e6b36b93764fd63322.tar.gz
rust-961fa632d678362b303678e6b36b93764fd63322.zip
Rollup merge of #83780 - matklad:doc-error-message, r=JohnTitor
Document "standard" conventions for error messages

These are currently documented in the API guidelines:

https://rust-lang.github.io/api-guidelines/interoperability.html#error-types-are-meaningful-and-well-behaved-c-good-err

I think it makes sense to uplift this guideline (in a milder form) into
std docs. Printing and producing errors is something that even
non-expert users do frequently, so it is useful to give at least some
indication of what a typical error message looks like.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions