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
Coming from this PR discussion, I wonder whether you guys have any experience with serialization performance from / to files (esp. on the JVM), an whether this library could be a good place to add a (maybe JVM-only) convenience function that uses either the string or the stream API for serialization, maybe even based on file length?
So far this project has only been focused on providing serializers, and utilities for writing serializers. I'm not really against adding it anyway though, as it's a sort-of generally useful companion to KxS. Would it make sense to add as a PR to kotlinx-serialization itself even?
If we choose to go ahead and add it in this project, my only wish is that we keep it tidy. Add the function as an extension to File or Path or something else appropriate, which the consumer would use to create a reference to the file.
Coming from this PR discussion, I wonder whether you guys have any experience with serialization performance from / to files (esp. on the JVM), an whether this library could be a good place to add a (maybe JVM-only) convenience function that uses either the string or the stream API for serialization, maybe even based on file length?
Please let me know what you think @Kantis et al!
The text was updated successfully, but these errors were encountered: