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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please elaborate on how we should proceed further with this suppress?
If this case is no longer supported (or was unsupported but not explicitly reported), shouldn't we have any kind of migration plan?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This suppress is a counterpart for
@Suppress("ACTUAL_FUNCTION_WITH_DEFAULT_ARGUMENTS")
. You can see that you already have a@Suppress("ACTUAL_FUNCTION_WITH_DEFAULT_ARGUMENTS")
insidepublic actual open class TestBase
.If you didn't have
@Suppress("ACTUAL_FUNCTION_WITH_DEFAULT_ARGUMENTS")
thenNO_ACTUAL_CLASS_MEMBER_FOR_EXPECTED_CLASS
wouldn't be reportedThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, I had to rework the way we report
ACTUAL_FUNCTION_WITH_DEFAULT_ARGUMENTS
. Before my changes, it was a separate checker. Now it's checked in the expect-actual matcher and it's considered a common expect-actual mismatch incompatibilityAnd such types of expect-actual mismatch incompatibilities are reported two times:
That's why you need to suppress
ACTUAL_FUNCTION_WITH_DEFAULT_ARGUMENTS
two times (But they are two separate diagnostics)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably it will be more clear If I change
Counterpart for ACTUAL_FUNCTION_WITH_DEFAULT_ARGUMENTS
comment toCounterpart for @Suppress("ACTUAL_FUNCTION_WITH_DEFAULT_ARGUMENTS")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The full compilation error of
NO_ACTUAL_CLASS_MEMBER_FOR_EXPECTED_CLASS
also makes it clear: