Module fs 

Re-exports

use std::path::Path; 🔒

use std::path::PathBuf; 🔒

use std::fs; 🔒

use std::io; 🔒

use rustc_data_structures::temp_dir::MaybeTempDir; 🔒

use rustc_fs_util::TempDirBuilder; 🔒

use rustc_middle::ty::TyCtxt; 🔒

use rustc_session::Session; 🔒

use rustc_session::config::OutFileName; 🔒

use rustc_session::config::OutputType; 🔒

use rustc_session::output::filename_for_metadata; 🔒

use rustc_span::ErrorGuaranteed; 🔒

use rustc_structures::CrateType; 🔒

use crate::diagnostics::BinaryOutputToTty; 🔒

use crate::diagnostics::FailedCopyToStdout; 🔒

use crate::diagnostics::FailedCreateEncodedMetadata; 🔒

use crate::diagnostics::FailedCreateFile; 🔒

use crate::diagnostics::FailedCreateTempdir; 🔒

use crate::diagnostics::FailedWriteError; 🔒

use crate::EncodedMetadata; 🔒

use crate::encode_metadata; 🔒

Constants

METADATA_FILENAME

Functions

copy_to_stdout

emit_wrapper_file

We use a temp directory here to avoid races between concurrent rustc processes, such as builds in the same directory using the same filename for metadata while building an .rlib (stomping over one another), or writing an .rmeta into a directory being searched for extern crate (observing an incomplete file). The returned path is the temporary file containing the complete metadata.

encode_and_write_metadata

non_durable_rename

This function attempts to bypass the auto_da_alloc heuristic implemented by some filesystems such as btrfs and ext4. When renaming over a file that already exists then they will “helpfully” write back the source file before committing the rename in case a developer forgot some of the fsyncs in the open/write/fsync(file)/rename/fsync(dir) dance for atomic file updates.