summaryrefslogtreecommitdiff
path: root/tests/rustdoc-js-std/parser-errors.js
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2023-02-15 21:31:00 +0100
committerGitHub <noreply@github.com>2023-02-15 21:31:00 +0100
commit55471015a0238f2fa2bf85adb38eb6bedf5ef26e (patch)
tree131dc4285eea8f12cb0c0be4151182a5ae6fc3ce /tests/rustdoc-js-std/parser-errors.js
parent863cd151321987eeaa89026e7661a8a68cb9ad81 (diff)
parent4c2d48ee800dd79bfb64b91ccee5262295fea9d5 (diff)
downloadrust-55471015a0238f2fa2bf85adb38eb6bedf5ef26e.tar.gz
Rollup merge of #108094 - kornelski:fsdocs, r=cuviper
Demonstrate I/O in File examples I've noticed that some Rust novices unnecessarily reinvent `std::fs::{read,write}`, presumably because they search for equivalents of `fopen` + `fwrite`. I've added links to `std::fs::{read,write}` in the docs. The `File` examples were only showing how to open a file, but not how to use the opened handle, unnecessarily leaving out the next step. I've added a variety of different uses of file handles to their examples in docs.
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions