Add execution tests for Drop behavior
GCC Rust compiler adds comprehensive tests for the `Drop` trait's behavior.
GCC Rust (gccrs) now includes additional execution tests covering various scenarios of the Drop trait. These new tests specifically target function parameter drop order, explicit returns, ownership transfers via function arguments and return values, and branch-local value drops. The goal is to ensure robust and correct handling of resource cleanup through the Drop trait in all supported contexts.
In Details
The gccrs testsuite has been expanded with new execution tests focusing on the behavior of the Drop trait. These tests cover aspects such as the drop order of function parameters, resource management around explicit return statements, ownership semantics during function calls and returns, and the lifetime of values within conditional branches. This broadens the test coverage for destructors and resource deallocation within gccrs.
- gccrs
- The GCC implementation of the Rust programming language compiler. It aims to compile Rust code using the GCC backend infrastructure.
- Drop trait
- A Rust trait that defines behavior for when a value goes out of scope. It's used for deterministic cleanup of resources, such as closing files or freeing memory.
- execution tests
- Tests that compile and run code to verify its runtime behavior, as opposed to static analysis or compile-time checks.
- ownership
- A core concept in Rust that manages memory safety. Each value in Rust has a unique owner, and when the owner goes out of scope, the value is dropped (and its destructor is called if it implements
Drop).