Skip to content

Conversation

natecook1000
Copy link
Member

@natecook1000 natecook1000 commented Feb 22, 2025

This change switches to simply printing the validation message to stderr and exiting with a failing error code, which possibly should have always been the behavior. This also revamps the file structure for validators.

Checklist

  • I've added at least one test that validates that my change is working, if appropriate
  • I've followed the code style of the rest of the project
  • I've read the Contribution Guidelines
  • I've updated the documentation if necessary

This also revamps the file structure for validators.
With backtrace support built into command-line Swift, calling `fatalError`
for configuration/validation errors isn't very effective, since the error
messages get hidden by the backtrace. This switches to simply printing
the validation message to stderr and exiting with a failing error code,
which possibly should have always been the behavior.
@rauhul
Copy link
Contributor

rauhul commented Feb 23, 2025

The cmake CI is very helpful!

@natecook1000
Copy link
Member Author

@swift-ci Please test

@natecook1000
Copy link
Member Author

@swift-ci Please test

@natecook1000 natecook1000 merged commit ef4f15f into main Feb 23, 2025
22 checks passed
@natecook1000 natecook1000 deleted the validation-tweaks branch February 23, 2025 14:30
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