Migrate TestElement interface to Kotlin #5959
Merged
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.
Description
This a transparent migration of TestElement interface to Kotiln.
Motivation and Context
Kotlin enables better nullability which is good both for Kotlin (compilation fails if null is passed to a method not expecting null), and Java (Kotlin compiler generates
@NotNull
annotations, so IDEs show when Java code does not handle nulls properly).Writing the interface in Kotlin enables the use of
operator fun get(property)
, andoperator fun set(property)
so it enables better APIs for Kotlin code. See #5946 (comment)Checklist: