Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for constructing const_region_t's from region_t&& #605

Closed
eyalroz opened this issue Mar 10, 2024 · 0 comments
Closed

Support for constructing const_region_t's from region_t&& #605

eyalroz opened this issue Mar 10, 2024 · 0 comments

Comments

@eyalroz
Copy link
Owner

eyalroz commented Mar 10, 2024

Our "enconstening" constructor for const_region_t current only takes const region_t&; but what about region_t&&?

@eyalroz eyalroz changed the title Support for constructing const_region_t's from const region_t& Support for constructing const_region_t's from region_t&& Mar 10, 2024
eyalroz added a commit that referenced this issue Mar 10, 2024
* `memory::region_t`'s are now CUDA-independent!
* `memory::const_region_t's` constructor from `region_t`'s is now by value rather than by const reference, so that rvalue-references are also supported
eyalroz added a commit that referenced this issue Mar 10, 2024
* `memory::region_t`'s are now CUDA-independent!
* `memory::const_region_t's` constructor from `region_t`'s is now by value rather than by const reference, so that rvalue-references are also supported
@eyalroz eyalroz self-assigned this Mar 10, 2024
eyalroz added a commit that referenced this issue Mar 10, 2024
* `memory::region_t`'s are now CUDA-independent!
* `memory::const_region_t's` constructor from `region_t`'s is now by value rather than by const reference, so that rvalue-references are also supported
eyalroz added a commit that referenced this issue Mar 10, 2024
* `memory::region_t`'s are now CUDA-independent!
* `memory::const_region_t's` constructor from `region_t`'s is now by value rather than by const reference, so that rvalue-references are also supported
eyalroz added a commit that referenced this issue Apr 20, 2024
* `memory::region_t`'s are now CUDA-independent!
* `memory::const_region_t's` constructor from `region_t`'s is now by value rather than by const reference, so that rvalue-references are also supported
eyalroz added a commit that referenced this issue Apr 29, 2024
* `memory::region_t`'s are now CUDA-independent!
* `memory::const_region_t's` constructor from `region_t`'s is now by value rather than by const reference, so that rvalue-references are also supported
@eyalroz eyalroz closed this as completed Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant