NVIDIA / NVIDIA/cccl

[BUG]: Thrust vector move ctor/assign/swap are not noexcept

Open
#1,991 2 comments 0 reactions 1 assignee Claimed by @bernhardmgruber View on GitHub
thrust
Dominant language
C++
Stars
2.5k
Forks
486
Avg merge
2d 6h
Merged PRs (30d)
295

Description

### Is this a duplicate?

- [X] I confirmed there appear to be no [duplicate issues](https://github.com/NVIDIA/cccl/issues) for this bug and that I agree to the [Code of Conduct](CODE_OF_CONDUCT.md)

### Type of Bug

Performance

### Component

Thrust

### Describe the bug

The move constructor and move assignment operators of Trust's vector types (`host_vector`, `device_vector` and `vector_base`) are not `noexcept` so their use in conjunction with the standard library may be unnecessarily pessimized (the standard library may copy types which's move operations are not `noexcept` to uphold exception safety guarantees). The same goes for the corresponding `swap` operations.

Furthermore, `contiguous_storage` only has a move assignment, but no move constructor, which is odd as well.

### How to Reproduce

N/A

### Expected behavior

N/A

### Reproduction link

_No response_

### Operating System

_No response_

### nvidia-smi output

_No response_

### NVCC version

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.