Skip to content

Conversation

@nickclark2016
Copy link
Member

What does this PR do?

Deprecates the NoRuntimeChecks flag. Adds a new API for `runtimechecks with the following fields:

  • Default (uses exporter defaults)
  • Off (performs no checks, maps to "Default" in IDE, maps to NoRuntimeChecks flag behavior)
  • StackFrame (stack frame checks)
  • UninitializedVariables (uninit variable checks)
  • FastChecks (all fast checks)

How does this PR change Premake's behavior?

No breaking changes

Anything else we should know?

Prep for 5.0

Did you check all the boxes?

  • Focus on a single fix or feature; remove any unrelated formatting or code changes
  • Add unit tests showing fix or feature works; all tests pass
  • Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
  • Follow our coding conventions
  • Minimize the number of commits
  • Align documentation to your changes

You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!

@nickclark2016 nickclark2016 requested a review from a team December 31, 2025 15:15
@nickclark2016 nickclark2016 force-pushed the remove-no-runtime-checks-flag branch from e11551d to 4206b4e Compare December 31, 2025 15:20
@redorav
Copy link
Collaborator

redorav commented Dec 31, 2025

Not quite sure I understand this comment:

Off (performs no checks, maps to "Default" in IDE, maps to NoRuntimeChecks flag behavior)

Particularly the "maps to Default" and "uses exporter defaults" bits, the comments in the docs do sound sensible but contradict the comment, am I reading these wrong?

@nickclark2016 nickclark2016 force-pushed the remove-no-runtime-checks-flag branch from 4206b4e to 9075ef5 Compare December 31, 2025 15:32
@nickclark2016
Copy link
Member Author

Not quite sure I understand this comment:

Off (performs no checks, maps to "Default" in IDE, maps to NoRuntimeChecks flag behavior)

Particularly the "maps to Default" and "uses exporter defaults" bits, the comments in the docs do sound sensible but contradict the comment, am I reading these wrong?

Yeah, I'm not sure what the best way to word this is. Basically, if we want to be "Default" in how Premake defines the default (aka don't emit a value and just let the exporter determine), we need to leave it empty. However, there is an explicit "Default" value in VS that actually maps better to "Off" (Microsoft sucks at naming). Would gladly take any wording suggestions here.

@nickclark2016 nickclark2016 force-pushed the remove-no-runtime-checks-flag branch from 9075ef5 to 0176b55 Compare December 31, 2025 15:50
@samsinsane samsinsane merged commit 2d7aec7 into premake:master Jan 1, 2026
55 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants