Move all "Default" asserts to debug

Open Beginner friendly
  • Is something wrong?
#842 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@hskang-amelia is already working on this.

Since Oct 26, 2026.

  • #853 by @hskang-amelia — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp
Domain
backend

Research direction

Search the repository for SCORE_LANGUAGE_FUTURECPP_ASSERT and SCORE_LANGUAGE_FUTURECPP_ASSERT_MESSAGE, then inspect the matching files and assertion definitions to confirm the debug equivalents. Replace each default assertion with its corresponding _DBG form. The work is done when neither original macro remains anywhere in the code.

Written by the indexing model from the issue text.

Description

cleanup good first issue
What

The current code uses a combination of all 3 levels of assertions however the 3 levels might be confusing and think we should move to just using either DBG asserts or PRD asserts.

Let's move all current "default" asserts to the debug level.
SCORE_LANGUAGE_FUTURECPP_ASSERT -> SCORE_LANGUAGE_FUTURECPP_ASSERT_DBG
SCORE_LANGUAGE_FUTURECPP_ASSERT_MESSAGE -> SCORE_LANGUAGE_FUTURECPP_ASSERT_DBG_MESSAGE

Acceptance Criteria (DoD)

No SCORE_LANGUAGE_FUTURECPP_ASSERT or SCORE_LANGUAGE_FUTURECPP_ASSERT_MESSAGE left in the code.

How

No response

Dominant language
C++
Stars
7
Forks
37
Avg merge
2d 9h
Merged PRs (30d)
117

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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 eclipse-score/lifecycle

All issues in eclipse-score/lifecycle

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.