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

[Suggestion] Make nob_needs_rebuild accept input paths as __VA_ARGS__

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c
Domain
build-system

Research direction

Start by locating the definitions of nob_needs_rebuild and nob_cmd_append in the header, then compare their argument handling with the proposed variadic macro example. Done means a clearly named interface accepts the shown output and input paths and the example compiles and preserves rebuild checking behavior.

Written by the indexing model from the issue text.

Description

nob_needs_rebuild is not very convenient to use. I suggest this macro(copied from nob_cmd_append):

#define foo(output_path, ...)                                                  \
    nob_needs_rebuild(                                                         \
        output_path, ((const char *[]){__VA_ARGS__}),                          \
        (sizeof((const char *[]){__VA_ARGS__}) / sizeof(const char *)))

if (foo("yyjson.o", "yyjson.c", "yyjson.h")) {
    // ...
}

We cannot use the name nob_nees_rebuild and I have no idea how to name it.

Dominant language
C++
Stars
3.3k
Forks
214
PR merge metrics
No merged PRs in 30d

Getting set up

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 tsoding/nob.h

All issues in tsoding/nob.h

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.