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
Path may be the best way to denote paths in modern Java, but File is still around, and String is more convenient than both. I think we should overload constructors that take Path to also take File and String, purely for ease-of-use. This pattern is common in Java and also Scala (e.g. scala.io.Source).
The text was updated successfully, but these errors were encountered:
I don't think we can overload if we are using default arguments which we do in the ZStream constructors for chunkSize. Perhaps we could have a naming convention like fromPath, fromFile, fromFileString? Or perhaps this is another push to developer a more compositional solution to the chunking problem.
Path
may be the best way to denote paths in modern Java, but File is still around, and String is more convenient than both. I think we should overload constructors that takePath
to also takeFile
andString
, purely for ease-of-use. This pattern is common in Java and also Scala (e.g.scala.io.Source
).The text was updated successfully, but these errors were encountered: