Suboptimal translation for std::deque

Open Beginner friendly
#610 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
79/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp, rust
Domain
compilers

Research direction

Start by locating the translation rule that maps std::deque to Vec; the issue does not name a file or test. Read how nearby C++ container translations choose Rust types, then check for tests covering std::deque. Done when std::deque translates to VecDeque and the relevant tests pass.

Written by the indexing model from the issue text.

Description

We translate std::deque as Vec. This results in suboptimal operations, e.g. std::deque::pop_front is O(1) in C++ and Vec::remove(0) is O(N).

Translate std::deque as VecDeque.

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.