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

Automated formatting

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
tooling

Research direction

Start by reviewing the library's current formatting practices and the existing .clang-format files in Boost modules such as gil, graph, histogram, multiprecision, nowide, outcome, and yap. Determine whether this library needs a dedicated configuration and what style it should enforce; done means an agreed .clang-format file is added without affecting unrelated Boost modules.

Written by the indexing model from the issue text.

Description

Would there be any interest in introducing a .clang-format file for this library? It would not set precedent for boost - gil, graph, histogram, multiprecision, nowide, outcome, and yap all currently have .clang-format files. As far as I can tell, those are each unique format files, so I think there would be large latitude to use any configuration that makes sense for this library.

Dominant language
C++
Stars
131
Forks
117
PR merge metrics
No merged PRs in 30d

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/algorithm

All issues in boostorg/algorithm

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.