Jake Wharton
Jake Wharton
I've never used either and don't recall their implementations. So, maybe?
Related to #1300
As written this doesn't work for file systems other than the system one, and doesn't work when the paths are on separate file systems (e.g., copying out of a zip).
Writing the signature as ```kotlin fun copy(srcFs: FileSystem, src: Path, dstFs: FileSystem, dst: Path) ``` Is more what I meant. This function works across file systems. You could also default...
Not sure how useful that is. It's the same as calling `apply`, only with a less powerful receiver type.
The point of a Buffer is mutability. Perhaps you're looking for `buildByteString`?
So something like ```kotlin fun buildByteString(body: Buffer.() -> Unit): ByteString = Buffer().apply(body).readByteString() ``` (or potentially with `Sink` as the lambda receiver) I'd say the argument for a function is slightly...
Unfortunately runtime behavior switching like that is not as viable as you may think. The use of method handles (or, presumably, var handles) involves generation of an `invokedynamic` instruction in...
It could be emulated with a separate Dex file that is conditionally loaded similar to how one might do a jar. But it likely has performance implications because of that...
> it seems that versioning this way just means having a separate cask definitions for each version? That is my understanding. They abandoned versioning a long time ago so this...