pub struct File { }
Expand description
An object providing access to an open file on the filesystem.
An instance of a File
can be read and/or written depending on what options it was opened with. Files also implement Seek
to alter the logical cursor that the file contains internally.
Files are automatically closed when they go out of scope. Errors detected on closing are ignored by the implementation of Drop
. Use the method sync_all
if these errors must be manually handled.
File
does not buffer reads and writes. For efficiency, consider wrapping the file in a BufReader
or BufWriter
when performing many small read
or write
calls, unless unbuffered reads and writes are required.
Creates a new file and write bytes to it (you can also use write
):
use std::fs::File;
use std::io::prelude::*;
fn main() -> std::io::Result<()> {
let mut file = File::create("foo.txt")?;
file.write_all(b"Hello, world!")?;
Ok(())
}
Reads the contents of a file into a String
(you can also use read
):
use std::fs::File;
use std::io::prelude::*;
fn main() -> std::io::Result<()> {
let mut file = File::open("foo.txt")?;
let mut contents = String::new();
file.read_to_string(&mut contents)?;
assert_eq!(contents, "Hello, world!");
Ok(())
}
Using a buffered Read
er:
use std::fs::File;
use std::io::BufReader;
use std::io::prelude::*;
fn main() -> std::io::Result<()> {
let file = File::open("foo.txt")?;
let mut buf_reader = BufReader::new(file);
let mut contents = String::new();
buf_reader.read_to_string(&mut contents)?;
assert_eq!(contents, "Hello, world!");
Ok(())
}
Note that, although read and write methods require a &mut File
, because of the interfaces for Read
and Write
, the holder of a &File
can still modify the file, either through methods that take &File
or by retrieving the underlying OS object and modifying the file that way. Additionally, many operating systems allow concurrent modification of files by different processes. Avoid assuming that holding a &File
means that the file will not change.
On Windows, the implementation of Read
and Write
traits for File
perform synchronous I/O operations. Therefore the underlying file must not have been opened for asynchronous I/O (e.g. by using FILE_FLAG_OVERLAPPED
).
Attempts to open a file in read-only mode.
See the OpenOptions::open
method for more details.
If you only need to read the entire file contents, consider std::fs::read()
or std::fs::read_to_string()
instead.
This function will return an error if path
does not already exist. Other errors may also be returned according to OpenOptions::open
.
use std::fs::File;
use std::io::Read;
fn main() -> std::io::Result<()> {
let mut f = File::open("foo.txt")?;
let mut data = vec![];
f.read_to_end(&mut data)?;
Ok(())
}
Source ð¬This is a nightly-only experimental API. (file_buffered
#130804)
Attempts to open a file in read-only mode with buffering.
See the OpenOptions::open
method, the BufReader
type, and the BufRead
trait for more details.
If you only need to read the entire file contents, consider std::fs::read()
or std::fs::read_to_string()
instead.
This function will return an error if path
does not already exist, or if memory allocation fails for the new buffer. Other errors may also be returned according to OpenOptions::open
.
#![feature(file_buffered)]
use std::fs::File;
use std::io::BufRead;
fn main() -> std::io::Result<()> {
let mut f = File::open_buffered("foo.txt")?;
assert!(f.capacity() > 0);
for (line, i) in f.lines().zip(1..) {
println!("{i:6}: {}", line?);
}
Ok(())
}
1.0.0 · Source
Opens a file in write-only mode.
This function will create a file if it does not exist, and will truncate it if it does.
Depending on the platform, this function may fail if the full directory path does not exist. See the OpenOptions::open
function for more details.
See also std::fs::write()
for a simple function to create a file with some given data.
use std::fs::File;
use std::io::Write;
fn main() -> std::io::Result<()> {
let mut f = File::create("foo.txt")?;
f.write_all(&1234_u32.to_be_bytes())?;
Ok(())
}
Source ð¬This is a nightly-only experimental API. (file_buffered
#130804)
Opens a file in write-only mode with buffering.
This function will create a file if it does not exist, and will truncate it if it does.
Depending on the platform, this function may fail if the full directory path does not exist.
See the OpenOptions::open
method and the BufWriter
type for more details.
See also std::fs::write()
for a simple function to create a file with some given data.
#![feature(file_buffered)]
use std::fs::File;
use std::io::Write;
fn main() -> std::io::Result<()> {
let mut f = File::create_buffered("foo.txt")?;
assert!(f.capacity() > 0);
for i in 0..100 {
writeln!(&mut f, "{i}")?;
}
f.flush()?;
Ok(())
}
1.77.0 · Source
Creates a new file in read-write mode; error if the file exists.
This function will create a file if it does not exist, or return an error if it does. This way, if the call succeeds, the file returned is guaranteed to be new. If a file exists at the target location, creating a new file will fail with AlreadyExists
or another error based on the situation. See OpenOptions::open
for a non-exhaustive list of likely errors.
This option is useful because it is atomic. Otherwise between checking whether a file exists and creating a new one, the file may have been created by another process (a TOCTOU race condition / attack).
This can also be written using File::options().read(true).write(true).create_new(true).open(...)
.
use std::fs::File;
use std::io::Write;
fn main() -> std::io::Result<()> {
let mut f = File::create_new("foo.txt")?;
f.write_all("Hello, world!".as_bytes())?;
Ok(())
}
1.58.0 · Source
Returns a new OpenOptions object.
This function returns a new OpenOptions object that you can use to open or create a file with specific options if open()
or create()
are not appropriate.
It is equivalent to OpenOptions::new()
, but allows you to write more readable code. Instead of OpenOptions::new().append(true).open("example.log")
, you can write File::options().append(true).open("example.log")
. This also avoids the need to import OpenOptions
.
See the OpenOptions::new
function for more details.
use std::fs::File;
use std::io::Write;
fn main() -> std::io::Result<()> {
let mut f = File::options().append(true).open("example.log")?;
writeln!(&mut f, "new line")?;
Ok(())
}
1.0.0 · Source
Attempts to sync all OS-internal file content and metadata to disk.
This function will attempt to ensure that all in-memory data reaches the filesystem before returning.
This can be used to handle errors that would otherwise only be caught when the File
is closed, as dropping a File
will ignore all errors. Note, however, that sync_all
is generally more expensive than closing a file by dropping it, because the latter is not required to block until the data has been written to the filesystem.
If synchronizing the metadata is not required, use sync_data
instead.
use std::fs::File;
use std::io::prelude::*;
fn main() -> std::io::Result<()> {
let mut f = File::create("foo.txt")?;
f.write_all(b"Hello, world!")?;
f.sync_all()?;
Ok(())
}
1.0.0 · Source
This function is similar to sync_all
, except that it might not synchronize file metadata to the filesystem.
This is intended for use cases that must synchronize content, but donât need the metadata on disk. The goal of this method is to reduce disk operations.
Note that some platforms may simply implement this in terms of sync_all
.
use std::fs::File;
use std::io::prelude::*;
fn main() -> std::io::Result<()> {
let mut f = File::create("foo.txt")?;
f.write_all(b"Hello, world!")?;
f.sync_data()?;
Ok(())
}
1.89.0 · Source
Acquire an exclusive lock on the file. Blocks until the lock can be acquired.
This acquires an exclusive lock; no other file handle to this file may acquire another lock.
This lock may be advisory or mandatory. This lock is meant to interact with lock
, try_lock
, lock_shared
, try_lock_shared
, and unlock
. Its interactions with other methods, such as read
and write
are platform specific, and it may or may not cause non-lockholders to block.
If this file handle/descriptor, or a clone of it, already holds a lock the exact behavior is unspecified and platform dependent, including the possibility that it will deadlock. However, if this method returns, then an exclusive lock is held.
If the file is not open for writing, it is unspecified whether this function returns an error.
The lock will be released when this file (along with any other file descriptors/handles duplicated or inherited from it) is closed, or if the unlock
method is called.
This function currently corresponds to the flock
function on Unix with the LOCK_EX
flag, and the LockFileEx
function on Windows with the LOCKFILE_EXCLUSIVE_LOCK
flag. Note that, this may change in the future.
On Windows, locking a file will fail if the file is opened only for append. To lock a file, open it with one of .read(true)
, .read(true).append(true)
, or .write(true)
.
use std::fs::File;
fn main() -> std::io::Result<()> {
let f = File::create("foo.txt")?;
f.lock()?;
Ok(())
}
Acquire a shared (non-exclusive) lock on the file. Blocks until the lock can be acquired.
This acquires a shared lock; more than one file handle may hold a shared lock, but none may hold an exclusive lock at the same time.
This lock may be advisory or mandatory. This lock is meant to interact with lock
, try_lock
, lock_shared
, try_lock_shared
, and unlock
. Its interactions with other methods, such as read
and write
are platform specific, and it may or may not cause non-lockholders to block.
If this file handle/descriptor, or a clone of it, already holds a lock, the exact behavior is unspecified and platform dependent, including the possibility that it will deadlock. However, if this method returns, then a shared lock is held.
The lock will be released when this file (along with any other file descriptors/handles duplicated or inherited from it) is closed, or if the unlock
method is called.
This function currently corresponds to the flock
function on Unix with the LOCK_SH
flag, and the LockFileEx
function on Windows. Note that, this may change in the future.
On Windows, locking a file will fail if the file is opened only for append. To lock a file, open it with one of .read(true)
, .read(true).append(true)
, or .write(true)
.
use std::fs::File;
fn main() -> std::io::Result<()> {
let f = File::open("foo.txt")?;
f.lock_shared()?;
Ok(())
}
1.89.0 · Source
Try to acquire an exclusive lock on the file.
Returns Err(TryLockError::WouldBlock)
if a different lock is already held on this file (via another handle/descriptor).
This acquires an exclusive lock; no other file handle to this file may acquire another lock.
This lock may be advisory or mandatory. This lock is meant to interact with lock
, try_lock
, lock_shared
, try_lock_shared
, and unlock
. Its interactions with other methods, such as read
and write
are platform specific, and it may or may not cause non-lockholders to block.
If this file handle/descriptor, or a clone of it, already holds a lock, the exact behavior is unspecified and platform dependent, including the possibility that it will deadlock. However, if this method returns Ok(())
, then it has acquired an exclusive lock.
If the file is not open for writing, it is unspecified whether this function returns an error.
The lock will be released when this file (along with any other file descriptors/handles duplicated or inherited from it) is closed, or if the unlock
method is called.
This function currently corresponds to the flock
function on Unix with the LOCK_EX
and LOCK_NB
flags, and the LockFileEx
function on Windows with the LOCKFILE_EXCLUSIVE_LOCK
and LOCKFILE_FAIL_IMMEDIATELY
flags. Note that, this may change in the future.
On Windows, locking a file will fail if the file is opened only for append. To lock a file, open it with one of .read(true)
, .read(true).append(true)
, or .write(true)
.
use std::fs::{File, TryLockError};
fn main() -> std::io::Result<()> {
let f = File::create("foo.txt")?;
match f.try_lock() {
Ok(_) => (),
Err(TryLockError::WouldBlock) => (), Err(TryLockError::Error(err)) => return Err(err),
}
f.try_lock()?;
Ok(())
}
Try to acquire a shared (non-exclusive) lock on the file.
Returns Err(TryLockError::WouldBlock)
if a different lock is already held on this file (via another handle/descriptor).
This acquires a shared lock; more than one file handle may hold a shared lock, but none may hold an exclusive lock at the same time.
This lock may be advisory or mandatory. This lock is meant to interact with lock
, try_lock
, lock_shared
, try_lock_shared
, and unlock
. Its interactions with other methods, such as read
and write
are platform specific, and it may or may not cause non-lockholders to block.
If this file handle, or a clone of it, already holds a lock, the exact behavior is unspecified and platform dependent, including the possibility that it will deadlock. However, if this method returns Ok(())
, then it has acquired a shared lock.
The lock will be released when this file (along with any other file descriptors/handles duplicated or inherited from it) is closed, or if the unlock
method is called.
This function currently corresponds to the flock
function on Unix with the LOCK_SH
and LOCK_NB
flags, and the LockFileEx
function on Windows with the LOCKFILE_FAIL_IMMEDIATELY
flag. Note that, this may change in the future.
On Windows, locking a file will fail if the file is opened only for append. To lock a file, open it with one of .read(true)
, .read(true).append(true)
, or .write(true)
.
use std::fs::{File, TryLockError};
fn main() -> std::io::Result<()> {
let f = File::open("foo.txt")?;
match f.try_lock_shared() {
Ok(_) => (),
Err(TryLockError::WouldBlock) => (), Err(TryLockError::Error(err)) => return Err(err),
}
f.try_lock_shared()?;
Ok(())
}
1.89.0 · Source
Release all locks on the file.
All locks are released when the file (along with any other file descriptors/handles duplicated or inherited from it) is closed. This method allows releasing locks without closing the file.
If no lock is currently held via this file descriptor/handle, this method may return an error, or may return successfully without taking any action.
§Platform-specific behaviorThis function currently corresponds to the flock
function on Unix with the LOCK_UN
flag, and the UnlockFile
function on Windows. Note that, this may change in the future.
On Windows, locking a file will fail if the file is opened only for append. To lock a file, open it with one of .read(true)
, .read(true).append(true)
, or .write(true)
.
use std::fs::File;
fn main() -> std::io::Result<()> {
let f = File::open("foo.txt")?;
f.lock()?;
f.unlock()?;
Ok(())
}
1.0.0 · Source
Truncates or extends the underlying file, updating the size of this file to become size
.
If the size
is less than the current fileâs size, then the file will be shrunk. If it is greater than the current fileâs size, then the file will be extended to size
and have all of the intermediate data filled in with 0s.
The fileâs cursor isnât changed. In particular, if the cursor was at the end and the file is shrunk using this operation, the cursor will now be past the end.
§ErrorsThis function will return an error if the file is not opened for writing. Also, std::io::ErrorKind::InvalidInput
will be returned if the desired length would cause an overflow due to the implementation specifics.
use std::fs::File;
fn main() -> std::io::Result<()> {
let mut f = File::create("foo.txt")?;
f.set_len(10)?;
Ok(())
}
Note that this method alters the content of the underlying file, even though it takes &self
rather than &mut self
.
Queries metadata about the underlying file.
§Examplesuse std::fs::File;
fn main() -> std::io::Result<()> {
let mut f = File::open("foo.txt")?;
let metadata = f.metadata()?;
Ok(())
}
1.9.0 · Source
Creates a new File
instance that shares the same underlying file handle as the existing File
instance. Reads, writes, and seeks will affect both File
instances simultaneously.
Creates two handles for a file named foo.txt
:
use std::fs::File;
fn main() -> std::io::Result<()> {
let mut file = File::open("foo.txt")?;
let file_copy = file.try_clone()?;
Ok(())
}
Assuming thereâs a file named foo.txt
with contents abcdef\n
, create two handles, seek one of them, and read the remaining bytes from the other handle:
use std::fs::File;
use std::io::SeekFrom;
use std::io::prelude::*;
fn main() -> std::io::Result<()> {
let mut file = File::open("foo.txt")?;
let mut file_copy = file.try_clone()?;
file.seek(SeekFrom::Start(3))?;
let mut contents = vec![];
file_copy.read_to_end(&mut contents)?;
assert_eq!(contents, b"def\n");
Ok(())
}
1.16.0 · Source
Changes the permissions on the underlying file.
§Platform-specific behaviorThis function currently corresponds to the fchmod
function on Unix and the SetFileInformationByHandle
function on Windows. Note that, this may change in the future.
This function will return an error if the user lacks permission change attributes on the underlying file. It may also return an error in other os-specific unspecified cases.
§Examplesfn main() -> std::io::Result<()> {
use std::fs::File;
let file = File::open("foo.txt")?;
let mut perms = file.metadata()?.permissions();
perms.set_readonly(true);
file.set_permissions(perms)?;
Ok(())
}
Note that this method alters the permissions of the underlying file, even though it takes &self
rather than &mut self
.
Changes the timestamps of the underlying file.
§Platform-specific behaviorThis function currently corresponds to the futimens
function on Unix (falling back to futimes
on macOS before 10.13) and the SetFileTime
function on Windows. Note that this may change in the future.
On most platforms, including UNIX and Windows platforms, this function can also change the timestamps of a directory. To get a File
representing a directory in order to call set_times
, open the directory with File::open
without attempting to obtain write permission.
This function will return an error if the user lacks permission to change timestamps on the underlying file. It may also return an error in other os-specific unspecified cases.
This function may return an error if the operating system lacks support to change one or more of the timestamps set in the FileTimes
structure.
fn main() -> std::io::Result<()> {
use std::fs::{self, File, FileTimes};
let src = fs::metadata("src")?;
let dest = File::open("dest")?;
let times = FileTimes::new()
.set_accessed(src.accessed()?)
.set_modified(src.modified()?);
dest.set_times(times)?;
Ok(())
}
1.75.0 · Source
Changes the modification time of the underlying file.
This is an alias for set_times(FileTimes::new().set_modified(time))
.
Available on Windows only.
1.0.0 · Source§ 1.0.0 · Source§Available on Windows only.
1.0.0 · Source§ 1.15.0 · Source§Available on Unix only.
Source§Reads a number of bytes starting from a given offset.
Read more Source§ ð¬This is a nightly-only experimental API. (unix_file_vectored_at
#89517)
Like
read_at
, except that it reads into a slice of buffers.
Read more Source§Writes a number of bytes starting from a given offset.
Read more Source§ ð¬This is a nightly-only experimental API. (unix_file_vectored_at
#89517)
Like
write_at
, except that it writes from a slice of buffers.
Read more 1.33.0 · Source§Reads the exact number of bytes required to fill
buf
from the given offset.
Read more 1.33.0 · Source§Attempts to write an entire buffer starting from a given offset.
Read more Source§Available on WASI only.
Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Reads a number of bytes starting from a given offset.
Read more Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Writes a number of bytes starting from a given offset.
Read more Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Adjusts the flags associated with this file.
Read more Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Adjusts the rights associated with this file.
Read more Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Provides file advisory information on a file descriptor.
Read more Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Forces the allocation of space in a file.
Read more Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213) Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Reads the contents of a symbolic link.
Read more Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Returns the attributes of a file or directory.
Read more Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213) Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213) Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Reads a number of bytes starting from a given offset.
Read more Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Reads the exact number of byte required to fill
buf
from the given offset.
Read more Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Writes a number of bytes starting from a given offset.
Read more Source§ ð¬This is a nightly-only experimental API. (wasi_ext
#71213)
Attempts to write an entire buffer starting from a given offset.
Read more 1.15.0 · Source§Available on Windows only.
1.63.0 · Source§ Source§Takes ownership of a File
âs underlying file descriptor.
Available on Windows only.
Source§Takes ownership of a File
âs underlying file handle.
File
will be converted to Stdio
using Stdio::from
under the hood.
use std::fs::File;
use std::process::Command;
let file = File::open("foo.txt")?;
let reverse = Command::new("rev")
.stdin(file) .output()?;
assert_eq!(reverse.stdout, b"!dlrow ,olleH");
1.63.0 · Source§ Source§
Returns a File
that takes ownership of the given file descriptor.
Available on Windows only.
Source§Returns a File
that takes ownership of the given handle.
Constructs a new instance of
Self
from the given raw file descriptor.
Read more 1.1.0 · Source§Available on Windows only.
1.4.0 · Source§ Source§Consumes this object, returning the raw underlying file descriptor.
Read more 1.4.0 · Source§Available on Windows only.
1.70.0 · Source§ 1.0.0 · Source§ Source§Reads some bytes from the file.
See Read::read
docs for more info.
This function currently corresponds to the read
function on Unix and the NtReadFile
function on Windows. Note that this may change in the future.
Like read
, except that it reads into a slice of buffers.
See Read::read_vectored
docs for more info.
This function currently corresponds to the readv
function on Unix and falls back to the read
implementation on Windows. Note that this may change in the future.
can_vector
#69941)
Determines if File
has an efficient read_vectored
implementation.
See Read::is_read_vectored
docs for more info.
This function currently returns true
on Unix an false
on Windows. Note that this may change in the future.
read_buf
#78485)
Pull some bytes from this source into the specified buffer.
Read more Source§Reads all bytes until EOF in this source, placing them into
buf
.
Read more Source§Reads all bytes until EOF in this source, appending them to
buf
.
Read more 1.6.0 · Source§Reads the exact number of bytes required to fill
buf
.
Read more Source§ ð¬This is a nightly-only experimental API. (read_buf
#78485)
Reads the exact number of bytes required to fill
cursor
.
Read more 1.0.0 · Source§Creates a âby referenceâ adaptor for this instance of
Read
.
Read more 1.0.0 · Source§ 1.0.0 · Source§Creates an adapter which will chain this stream with another.
Read more 1.0.0 · Source§Creates an adapter which will read at most
limit
bytes from it.
Read more 1.0.0 · Source§ Source§Pull some bytes from this source into the specified buffer, returning how many bytes were read.
Read more Source§Like
read
, except that it reads into a slice of buffers.
Read more Source§ ð¬This is a nightly-only experimental API. (read_buf
#78485)
Pull some bytes from this source into the specified buffer.
Read more Source§ ð¬This is a nightly-only experimental API. (can_vector
#69941)
Determines if this
Read
er has an efficient
read_vectored
implementation.
Read more Source§Reads all bytes until EOF in this source, placing them into
buf
.
Read more Source§Reads all bytes until EOF in this source, appending them to
buf
.
Read more 1.6.0 · Source§Reads the exact number of bytes required to fill
buf
.
Read more Source§ ð¬This is a nightly-only experimental API. (read_buf
#78485)
Reads the exact number of bytes required to fill
cursor
.
Read more 1.0.0 · Source§Creates a âby referenceâ adaptor for this instance of
Read
.
Read more 1.0.0 · Source§ 1.0.0 · Source§Creates an adapter which will chain this stream with another.
Read more 1.0.0 · Source§Creates an adapter which will read at most
limit
bytes from it.
Read more 1.0.0 · Source§ Source§Seek to an offset, in bytes in a file.
See Seek::seek
docs for more info.
This function currently corresponds to the lseek64
function on Unix and the SetFilePointerEx
function on Windows. Note that this may change in the future.
seek_stream_len
#59359)
Returns the length of this file (in bytes).
See Seek::stream_len
docs for more info.
This function currently corresponds to the statx
function on Linux (with fallbacks) and the GetFileSizeEx
function on Windows. Note that this may change in the future.
Returns the current seek position from the start of the stream.
Read more 1.55.0 · Source§Rewind to the beginning of a stream.
Read more 1.80.0 · Source§Seeks relative to the current position.
Read more 1.0.0 · Source§ 1.0.0 · Source§ Source§Writes some bytes to the file.
See Write::write
docs for more info.
This function currently corresponds to the write
function on Unix and the NtWriteFile
function on Windows. Note that this may change in the future.
Like write
, except that it writes into a slice of buffers.
See Write::write_vectored
docs for more info.
This function currently corresponds to the writev
function on Unix and falls back to the write
implementation on Windows. Note that this may change in the future.
can_vector
#69941)
Determines if File
has an efficient write_vectored
implementation.
See Write::is_write_vectored
docs for more info.
This function currently returns true
on Unix an false
on Windows. Note that this may change in the future.
Flushes the file, ensuring that all intermediately buffered contents reach their destination.
See Write::flush
docs for more info.
Since a File
structure doesnât contain any buffers, this function is currently a no-op on Unix and Windows. Note that this may change in the future.
Attempts to write an entire buffer into this writer.
Read more Source§ ð¬This is a nightly-only experimental API. (write_all_vectored
#70436)
Attempts to write multiple buffers into this writer.
Read more 1.0.0 · Source§Writes a formatted string into this writer, returning any error encountered.
Read more 1.0.0 · Source§Creates a âby referenceâ adapter for this instance of
Write
.
Read more 1.0.0 · Source§ Source§Writes a buffer into this writer, returning how many bytes were written.
Read more Source§ Source§ ð¬This is a nightly-only experimental API. (can_vector
#69941) Source§
Flushes this output stream, ensuring that all intermediately buffered contents reach their destination.
Read more 1.0.0 · Source§Attempts to write an entire buffer into this writer.
Read more Source§ ð¬This is a nightly-only experimental API. (write_all_vectored
#70436)
Attempts to write multiple buffers into this writer.
Read more 1.0.0 · Source§Writes a formatted string into this writer, returning any error encountered.
Read more 1.0.0 · Source§Creates a âby referenceâ adapter for this instance of
Write
.
Read moreRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4