assert_separately: Suppress experimental warnings #21
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.
test-unit depends on power_assert that the recent versions require ruby 3.1 or later. While test-unit rescues syntax error at loading power_assert for old ruby versions, warnings for experimental features are not suppressed, and
assert_separatelyfails because stderr is not empty, by default. Since addingrequired_ruby_versionto power_assert causes the installation with old rubygems to fail, we just ignore warnings for experimental features totally.