Improved Kotlin bf2. #174
Open
Improved Kotlin bf2. #174
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Better code style. Avoid unnecessary allocations. Removed warming.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Better code style (use Kotlin stdlib rather than Java's where possible).
Avoid unnecessary allocations.
Removed warming.
On my machine, with Oracle's JDK 8, I observed an improvement when running the warming program from 1.3 seconds to 1.2 seconds.
This is extremely fast, much faster than Go for example, even including the JVM startup time!
Even the Java optimised implementation I submitted on #173, running with the GraalVM JIT, is not as fast!