2.x: Add dematerialize(selector), deprecate old #6281
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.
This PR adds the
dematerialize(Function<T, Notification<R>> selector)overload to allow type-safe dematerialization ofNotificationsignals. The pre-existingdematerialize()forced the return type and assumed the items of the source areNotificationobjects, which could not be enforced via the type system. This selector variant establishes the type link fromTtoNotification<R>toR(where R == T is allowed).The intended use is
aka identity mapping.
The pre-existing
dematerialize()methods are marked as deprecated now.(Also the actual operator were missing from the examples in the respective Javadocs).