Skip to content

Exchange the explicit mapper classes through lambdas #27

Closed
@roookeee

Description

datus currently implements the Mapper<A,B> in two distinct classes for the mutable and immutable API. This is unnecessary as the Mapper<A,B> interface is a functional interface. As the mapper implementation classes are package private this is a non-breaking change that reduces the overall code size of datus while also opening up for future JVM optimizations in regards to lambdas. Some local JMH testing also showed minor performance benefits when using lambdas.

Activity

self-assigned this
on Aug 27, 2019
roookeee

roookeee commented on Aug 27, 2019

@roookeee
OwnerAuthor

Implementation is in branch issue-27 - will probably release 1.3.1 for this

roookeee

roookeee commented on Aug 29, 2019

@roookeee
OwnerAuthor

Will merge into develop soon but won't release as of yet (too little has changed to release 1.3.1 or 1.4.0)

added a commit that references this issue on Sep 3, 2019

ISSUE-27(#27): Exchange the explicit mapper classes through lambdas

roookeee

roookeee commented on Sep 3, 2019

@roookeee
OwnerAuthor

Merged into develop

added this to the 1.4.1 milestone on Sep 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Exchange the explicit mapper classes through lambdas · Issue #27 · roookeee/datus