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

[C++] Make Headers multi-thread safe

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
tooling

Research direction

No files or tests are named. Start by locating the generated C++ headers and reviewing how objects are accessed concurrently; the issue does not define whether locking is required, optional, or what completion criteria should be used, so the synchronization design needs clarification first.

Written by the indexing model from the issue text.

Description

Currently headers are not multi-thread-safe, and the calling application needs to take care on having the right multithread-behaviour.

A simple optional (?) option would be to introduce a header-mutex with a lockguard on each object. This introduces a memory overhead, but would make concurrent calls possible if they are on separate objects.

Dominant language
Go
Stars
54
Forks
26
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 Autodesk/AutomaticComponentToolkit

All issues in Autodesk/AutomaticComponentToolkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.