Skip to content

setopt: refactor out the booleans from setopt_long to setopt_bool#17887

Closed
bagder wants to merge 1 commit intomasterfrom
bagder/setopt-bool
Closed

setopt: refactor out the booleans from setopt_long to setopt_bool#17887
bagder wants to merge 1 commit intomasterfrom
bagder/setopt-bool

Conversation

@bagder
Copy link
Member

@bagder bagder commented Jul 10, 2025

  • add a warning if a boolean is set to something not 1 or 0 (as it might be made to mean something else in a future)

  • use 's->' in all setopt_* functions

@bagder bagder added the tidy-up label Jul 10, 2025
@bagder bagder marked this pull request as ready for review July 10, 2025 13:41
@testclutch

This comment was marked as outdated.

bagder added a commit that referenced this pull request Jul 16, 2025
- add a message if a boolean is set to something not 1 or 0 (as it might be
  made to mean something else in a future)

- use 's->' in all setopt_* functions

Closes #17887
@bagder bagder force-pushed the bagder/setopt-bool branch from e88fe72 to c013767 Compare July 16, 2025 10:47
- add a message if a boolean is set to something not 1 or 0 (as it might be
  made to mean something else in a future)

- use 's->' in all setopt_* functions

Closes #17887
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

2 participants