Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

vector_indexing_suite should implement MutableSequence

Open
#367 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, python

Research direction

Start from the vector_indexing_suite implementation and compare its existing methods with the MutableSequence method table in the linked Python documentation. Add insert, reverse, pop, remove, and iadd so the exposed vector satisfies MutableSequence; investigate map_indexing_suite only if its analogous gap is relevant.

Written by the indexing model from the issue text.

Description

Currently vector_indexing_suite implements a few methods that you would expect from list but not all. It means I have to put this type in my_cpp_modules.pyi:

class vector(Iterable[T], Container[T], Sized):
  # From indexing_suite
  def __len__(self) -> int: ...
  def __setitem__(self, index: int, value: T) -> None: ...
  def __delitem__(self, index: int) -> None: ...
  def __getitem__(self, index: int) -> T: ...
  def __contains__(self, value: T) -> bool: ...
  def __iter__(self) -> int: ...
  # From vector_indexing_suite
  def append(self, v: T) -> None: ...
  def extend(self, v: Any) -> None: ...

Instead of deriving from Iterable[T], Container[T], Sized it would be much better if it were just a MutableSequence[T]. However that needs a few more methods (see the table at the top of this page):

Specifically:

  • insert
  • reverse
  • pop
  • remove
  • __iadd__

Those methods should be added. It looks like it should be pretty easy.

A similar issue may exist for map_indexing_suite/MutableMapping but I haven't used it yet.

Dominant language
C++
Stars
537
Forks
223
Avg merge
11h 22m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

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 boostorg/python

All issues in boostorg/python

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.