diff
diff copied to clipboard
pkg
``` $ go version go version devel +dec3d00b28 Thu Mar 25 04:21:29 2021 +0000 linux/amd64 ``` ``` $ go env GO111MODULE="" GOARCH="amd64" GOBIN="" GOCACHE="/home/myitcv/.cache/go-build" GOENV="/home/myitcv/.config/go/env" GOEXE="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOINSECURE=""...
Should we do terminal detection automatically? See e.g. https://github.com/tailscale/depaware/issues/11. It would add significant dependencies, which is unfortunate. Perhaps we should instead provide easily copy/paste-able code that does it? Or maybe...
I used them for a project long ago, as a way to easily have portable and readable "edit scripts" to go from plaintext file A to B. You can see...
I have been thinking about making a push to get this to v1.0. The main problem is the API. The current API is unwieldy: it is a blend of high...
Consider this diff: ```diff @@ -441,8 +441,26 @@ func (v *ReferenceNameIterator) Next() (string, error) { return C.GoString(ptr), nil } -// Next retrieves the next reference. If the iterationis over, the...
As I was reading the `TODO: better name` on `DiffWriteable`, I thought to myself - is there a good reason to separate the interfaces? Unifying them would fix the naming...
The README says that we're waiting for generics. This issue can serve as a place to discuss that, as the generic proposals roll in. Unfortunately, the latest generic proposal (summer...
I was just thinking that most of the types one might want to diff can already be compared for equality, as per the language spec. So, we could add `func...
That is, `func Files(left, right string) DiffWriteable`. It would read the contents of the files up-front and diff the lines as `[]string` or `[][]byte`, while including the original filenames. It...