gccrs: Use std::move to reduce copy constructor usage.
Reduces unnecessary object copies in type-bound predicate handling.
This commit refactors several type-checking functions within gccrs to use std::move instead of direct copying. This change aims to reduce the usage of copy constructors for type-bound predicates, potentially improving performance by avoiding redundant object creations and copies during the type-checking process.
In Details
The gccrs typechecker, specifically within the typecheck directory, has been refactored to use std::move in functions like TypeCheckContext::insert_resolved_predicate and TypeBoundPredicate::TypeBoundPredicate. This change targets areas where objects were being copied when a move would suffice, aiming to optimize the handling of type-bound predicates and associated mappings.
- type-bound predicate
- In Rust, a type-bound predicate (often related to traits) specifies requirements that a type must meet. In the context of gccrs, these predicates are crucial during type checking to ensure type correctness and adherence to trait bounds.
- copy constructor
- A special constructor in C++ used to create a new object as a copy of an existing object. While convenient, excessive use can lead to performance overhead due to data duplication.
- std::move
- A C++ standard library function that enables an object to be "moved" rather than copied. This is typically used for resources like dynamically allocated memory, transferring ownership from the source object to the destination object, often leaving the source in a valid but unspecified state.