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
This makes them a less useful reference for people trying to figure out how to set up kx.benchmark in their own project than they could potentially be.
Given that there's plenty of people who are quite proficient in Kotlin and want to be able to benchmark their code, but who aren't as comfortable in configuring Gradle, it would be great to have the samples depend on the library versions that are available on Maven Central instead, so that their configurations build.gradle.kts etc are more copy-pastable and usable as direct references.
The text was updated successfully, but these errors were encountered:
I totally agree that samples should refer to a published artifacts. However, it would be nice to have a way to substitute a custom version of the plugin (and its runtime library) via some Gradle property. It'll allow running examples in CI against the current plugin version and it may help catching some issues earlier (otherwise, it's hard to ensure that examples continue to work with a new version before publishing that version).
Howdy! 🤠
Currently, examples depend on the surrounding project:
This makes them a less useful reference for people trying to figure out how to set up kx.benchmark in their own project than they could potentially be.
Given that there's plenty of people who are quite proficient in Kotlin and want to be able to benchmark their code, but who aren't as comfortable in configuring Gradle, it would be great to have the samples depend on the library versions that are available on Maven Central instead, so that their configurations
build.gradle.kts
etc are more copy-pastable and usable as direct references.The text was updated successfully, but these errors were encountered: