fix NaN for functional-if-then-else #6537
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Goober5000
added
fix
wookieejedi
approved these changes
Jan 20, 2025
Any NaN encountered in the evaluation of functional-if-then-else should be isolated to the branch on which it occurs. Fixes scp-fs2open#6536. Also improve some help text for clarity.
Goober5000
force-pushed
the
functional_if_then_else_fix
branch
from
f5cef24 to
a606ed7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Any NaN encountered in the evaluation of
functional-if-then-elseshould be isolated to the branch on which it occurs. Fixes #6536.Also improve some help text for clarity.