Make configuration accept unknown-but-maybe-valid-in-the-future options #14624
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.
This fixes #14615, which is reported as a 1.8.1 regression but was actually reproducible even before with
meson configure
(instead ofmeson setup --reconfigure
).It's not trivial fix, though in the end the code becomes almost simpler. The crux of the issue is the disagreement between
OptionStore.validate_cmd_line_options
,MesonApp.check_unused_options
andOptionStore.set_option_from_string
. Place the desired semantics (mostly those fromcheck_unused_options
) in a new function so that the three share the same logic.Fixes: #14615