Move/copy ctor and destructor do not run on std::vector reallocation

Open
#587 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, rust
Domain
backend, compilers

Research direction

Start by locating the Vec<T> translation and its tests, then trace how it handles std::vector reallocation. Compare the translated behavior with C++ move or copy construction and destruction of old elements during reallocation. Done means the translation preserves those constructor and destructor calls; the issue does not name a specific test or file.

Written by the indexing model from the issue text.

Description

When a std::vector reallocates the move constructor (or copy constructor is move is not marked noexcept) is called. The destructor is also called on the old elements.

Our Vec<T> translation does not respect that.

Dominant language
Rust
Stars
310
Forks
18
Avg merge
10h 18m
Merged PRs (30d)
125

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Cpp2Rust/cpp2rust

All issues in Cpp2Rust/cpp2rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.