std::filesy...resize_file(3)

πŸ“¦ version 2024.07.05, in nixpkgs unstable, opensuse-leap 16.0

πŸ’… std::filesystem::resize_file πŸ’…

okay so bestie, this is the std::filesy...resize_file(3) page from the C++ Standard Libary manual β€” yes, the header is literally truncated with dots, and yes, we are respecting the lore πŸ’€. It covers std::filesystem::resize_file, and it’s all about changing the size of a regular file. let’s go. ✨


🌸 NAME 🌸

std::filesystem::resize_file - std::filesystem::resize_file.

that’s the whole name section. it ate and left no crumbs. πŸ’…


✨ Synopsis ✨

Defined in header <filesystem>:

void resize_file( const std::filesystem::path& p, (1) (since C++17)
                  std::uintmax_t new_size );
void resize_file( const std::filesystem::path& p,

                  std::uintmax_t new_size,        (2) (since C++17)

                  std::error_code& ec ) noexcept;

so what does it do? It changes the size of the regular file named by p as if by POSIX truncate: if the file size was previously larger than new_size, the remainder of the file is discarded. If the file was previously smaller than new_size, the file size is increased and the new area appears as if zero-filled. that’s the tea πŸ«–.


πŸŽ€ Parameters πŸŽ€

  • p β€” path to resize.
  • new_size β€” size that the file will now have.
  • ec β€” out-parameter for error reporting in the non-throwing overload.

πŸ’– Return value πŸ’–

(none) β€” literally no return value, bestie. periodt. πŸ’–


πŸ”₯ Exceptions πŸ”₯

Any overload not marked noexcept may throw std::bad_alloc if memory allocation fails.

  1. Throws std::filesystem::filesystem_error on underlying OS API errors, constructed with p as the first path argument and the OS error code as the error code argument.
  2. Sets a std::error_code& parameter to the OS API error code if an OS API call fails, and executes ec.clear() if no errors occur.

πŸ¦‹ Notes πŸ¦‹

On systems that support sparse files, increasing the file size does not increase the space it occupies on the file system: space allocation takes place only when non-zero bytes are written to the file.

like, the file can be bigger without eating more space until you actually write non-zero bytes into it β€” sparse-file magic, iykyk. πŸ¦‹


🌈 Example 🌈

Demonstrates the effect creating a sparse file has on the free space.

the page also has this line before the code: // Run this code. preserving it for the culture:

        #include <filesystem>
        #include <fstream>
        #include <iostream>
        #include <locale>

        int main()
        {
            auto p = std::filesystem::temp_directory_path() / "example.bin";
            std::ofstream{p}.put('a');
            std::cout.imbue(std::locale{"en_US.UTF8"});
            std::cout << "File size:  " << std::filesystem::file_size(p) <<
       '\n'
                      << "Free space: " << std::filesystem::space(p).free <<
       '\n';
            std::filesystem::resize_file(p, 64*1024); // resize to 64 KB
            std::cout << "File size:  " << std::filesystem::file_size(p) <<
       '\n'
                      << "Free space: " << std::filesystem::space(p).free <<
       '\n';
            std::filesystem::remove(p);
        }

⭐ Possible output ⭐

and the possible output is literally this, commas and all:

        File size:  1
        Free space: 42,954,108,928
        File size:  65,536
        Free space: 42,954,108,928

πŸ‘‘ See also πŸ‘‘

  • file_size β€” returns the size of a file (C++17) (function).
  • space β€” determines available free space on the file system (C++17) (function).

mwah πŸ’‹ sign-off: this page came from http://cppreference.com, version/date 2024.06.10, and the footer name is std::filesy...resize_file(3). go resize something, bestie. πŸŽ€

πŸ“¦ where this page comes from