Skip to content

Conversation

@TheOddler
Copy link
Contributor

I found the description that mentions if-then-else while it's more like a if-NOT-then-else confusing. So thought it better that it actually mentions Data.Bool.bool as it's mirroring that.

I wonder, is it also worth adding an actual ifThenElse = flip bool function, might be more intuitive?



-- | An if-then-else expression on tables.
-- | Case analysis for an @Expr Bool@. Corresponds to 'Data.Bool.bool'.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using the wording "Case analysis" from the description of Data.Bool.Bool, and the "Corresponding to ..." from the description of Rel8.Expr.Bool.boolExpr. Sound OK I guess?

@TeofilC
Copy link
Contributor

TeofilC commented Oct 16, 2025

Thanks this is a lot clearer!

@TeofilC TeofilC enabled auto-merge (squash) October 16, 2025 22:33
@TeofilC TeofilC merged commit 7969088 into circuithub:master Oct 16, 2025
1 check 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.

2 participants