Some minor improvements to the scala code #19
Conversation
This file contains 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
The result is slightly faster parsing and much faster serialization * close files after reading with `Using.resource` * stop splitting lines by comma after reaching enough elements * simplify index-creation by using `getOrElseUpdate` * scala3-style indentation over curly brackets * use += over addOne as most scala-code tends to do * avoid double lookup in `schedulesForRoute`, by looping over both the option and its content * switched from upickle to jsoniter-scala to improve serialization speed * added application/json content-type
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The result is slightly faster parsing and much faster serialization
Using.resourcegetOrElseUpdate+=overaddOneas most scala-code tends to doschedulesForRoute, by looping over both the option and its content