a structural diff that understands syntax 🟥🟩
 
 
 
 
 
Go to file
Wilfred Hughes 426ce9751f Defer edge calculations
This saves 1.3% instructions and 7% peak memory usage (because the
predecessors hash map has smaller size values).
2022-05-29 11:32:44 +07:00
.github ci: Use stable rust for code coverage 2022-05-03 15:56:59 +07:00
img New screenshots and add screencast demo 2022-03-26 15:46:41 +07:00
manual Tweak slogan to clarify that difftastic understands structure 2022-05-23 23:39:15 +07:00
sample_files Prefer outer delimiter in lisps 2022-05-11 11:54:02 +07:00
scripts cargo publish is now done by GitHub action 2022-04-10 15:39:02 +07:00
src Defer edge calculations 2022-05-29 11:32:44 +07:00
vendor Add Elvish support 2022-05-07 20:12:43 +07:00
.codecov.yml Disable codecov comments on PRs 2022-04-22 00:53:48 +07:00
.gitattributes Ignore sample files for calculating GitHub code statistics 2022-01-16 20:27:11 +07:00
.gitignore Ignore temporary file from comparison tool 2022-02-13 17:16:30 +07:00
CHANGELOG.md Document MIME database configuration and paths 2022-05-19 23:19:54 +07:00
CITATION.cff Add citation information 2021-11-23 09:52:39 +07:00
Cargo.lock Update dependencies 2022-05-23 22:36:37 +07:00
Cargo.toml Prefer a complete sentence 2022-05-29 09:57:54 +07:00
LICENSE Roll year 2022-02-05 15:58:45 +07:00
README.md Tweak slogan to clarify that difftastic understands structure 2022-05-23 23:39:15 +07:00
build.rs Add Elvish support 2022-05-07 20:12:43 +07:00
rust-toolchain.toml Update rust-toolchain.toml 2022-05-08 02:48:12 +07:00
text_diff_notes.md Add notes on LCS weaknesses 2021-03-21 13:34:01 +07:00

README.md

it's difftastic!
manual crates.io codecov.io

Difftastic is a structural diff tool that compares files based on their syntax.

For installation instructions, see Installation in the manual.

Basic Example

Screenshot of difftastic and JS

In this JavaScript example, we can see:

(1) Difftastic understands nesting. It highlights the matching { and }, but understands that foo() hasn't changed despite the leading whitespace.

(2) Difftastic understands which lines should be aligned. It's aligned bar() on the left with bar(1) on the right, despite their changes.

(3) Difftastic understands that line-wrapping isn't meaningful. "eric" is now on a new line, but it hasn't changed.

One Minute Demo

asciicast

This one minute screencast demonstrates difftastic usage with both standalone files and git.

Languages

Difftastic supports over 20 programming languages, see the manual for the full list.

If a file has an unrecognised extension, difftastic uses a textual diff with word highlighting.

Known Issues

Performance. Difftastic scales relatively poorly on files with a large number of changes, and can use a lot of memory.

Display. Difftastic has a side-by-side display which usually works well, but can be confusing.

Robustness. Difftastic regularly has releases that fix crashes.

Non-goals

Patching. Difftastic output is intended for human consumption, and it does not generate patches that you can apply later. Use diff if you need a patch.

(Patch files are also line-oriented, which is too limited for difftastic. Difftastic might find additions and removals on the same line, and it tracks the relationship between line numbers in the old and new file.)

Merging. AST merging is a hard problem that difftastic does not address.

FAQ

Isn't this basically --word-diff --ignore-all-space?

Word diffing can't do this.

Difftastic parses your code. It understands when whitespace matters, such as inside string literals or languages like Python. It understands that x-1 is three tokens in JS but one token in Lisp.

Can I use difftastic with git?

You can! The difftastic manual includes instructions for git usage. You can also use it with mercurial.

Does difftastic integrate with my favourite tool?

Probably not. Difftastic is young. Consider writing a plugin for your favourite tool, and I will link it in the README!

License

Difftastic is open source under the MIT license, see LICENSE for more details.

This repository also includes tree-sitter parsers by other authors in the vendor/ directory. These are a mix of the MIT license and the Apache license. See vendor/*/LICENSE for more details.

Files in sample_files/ are also under the MIT license unless stated otherwise in their header.