about summary refs log tree commit diff
path: root/compiler/rustc_codegen_cranelift/example/std_example.rs
diff options
context:
space:
mode:
authorStuart Cook <Zalathar@users.noreply.github.com>2024-09-12 20:37:14 +1000
committerGitHub <noreply@github.com>2024-09-12 20:37:14 +1000
commit8e037ccec74dd536173ba60f12e724f4c2ad5ef9 (patch)
tree0fee5119903b0aea937ee7b2b278984627d06c7a /compiler/rustc_codegen_cranelift/example/std_example.rs
parent7c7372b6a1b9a8d6b787a3e5a10e4f8325b1fdfc (diff)
parent45c471b1f3421fff4f29fae80d507831c836f40f (diff)
downloadrust-8e037ccec74dd536173ba60f12e724f4c2ad5ef9.tar.gz
rust-8e037ccec74dd536173ba60f12e724f4c2ad5ef9.zip
Rollup merge of #125060 - ChrisJefferson:pathbuf-doc, r=workingjubilee
Expand documentation of PathBuf, discussing lack of sanitization

Various methods in `PathBuf`, in particular `set_file_name` and `set_extension` accept strings which include path seperators (like `../../etc`). These methods just glue together strings, so you can end up with strange strings.

This isn't reasonable to change/fix at this point, and might not even be fixable, but I think should be documented. In particular, you probably shouldn't blindly build paths using strings given by possibly malicious users.
Diffstat (limited to 'compiler/rustc_codegen_cranelift/example/std_example.rs')
0 files changed, 0 insertions, 0 deletions