You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@dinomite great minds etc; I was just thinking about this the other day. It might make sense to create slightly different set of tests (could still use same MediaItem) to contrast maybe "vanilla" Java with Kotlin (and maybe even Scala?), and possibly one or two other formats just as sanity checks. But not necessarily add new dimension for existing tests.
I think json backend should give a reasonable idea of differences.
Although one reason for using maybe different Bean type would be to use more varied features. Regardless, due to Kotlin's (and Scala's if included) heavier use of Creators, should probably use argument-taking constructors even if with MediaItem, to more accurately represent common usage patterns.
As a background MediaItem was used for convenience and to relate to then-popular JVM benchmark:
There is a set of performance tests for Jackson but none of them use the Kotlin module currently.
The text was updated successfully, but these errors were encountered: