[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-5378":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":24,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":28,"readmeContent":29,"aiSummary":30,"trendingCount":16,"starSnapshotCount":16,"syncStatus":31,"lastSyncTime":32,"discoverSource":33},5378,"difftastic","Wilfred\u002Fdifftastic","Wilfred","a structural diff that understands syntax 🟥🟩","https:\u002F\u002Fdifftastic.wilfred.me.uk\u002F",null,"Rust",25473,485,60,239,0,26,189,10,43.06,"MIT License",false,"master",true,[26,27],"diff","tree-sitter","2026-06-12 02:01:09","\u003Cp align=\"center\">\n  \u003Ca href=\"#readme\">\u003Cimg src=\"img\u002Flogo.png\" alt=\"it's difftastic!\"\u002F>\u003C\u002Fa>\n  \u003Cbr>\n  \u003Ca href=\"https:\u002F\u002Fdifftastic.wilfred.me.uk\u002Fintroduction.html\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fmanual-en-brightgreen?style=plastic\" alt=\"English manual\">\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fdifftastic.wilfred.me.uk\u002Fzh-CN\u002F\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fmanual-zh--CN-brightgreen?style=plastic\" alt=\"Chinese manual\">\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fcrates.io\u002Fcrates\u002Fdifftastic\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fcrates\u002Fv\u002Fdifftastic.svg?style=plastic\" alt=\"crates.io\">\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fcodecov.io\u002Fgh\u002FWilfred\u002Fdifftastic\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fcodecov\u002Fc\u002Fgithub\u002FWilfred\u002Fdifftastic?style=plastic&token=dZzAZtQT2S\" alt=\"codecov.io\">\u003C\u002Fa>\n\u003C\u002Fp>\n\nDifftastic is a structural diff tool that compares files based on\ntheir syntax.\n\n**For installation instructions, see\n[Installation](https:\u002F\u002Fdifftastic.wilfred.me.uk\u002Finstallation.html) in\n[the manual](https:\u002F\u002Fdifftastic.wilfred.me.uk\u002F).**\n\n## Examples\n\n![Screenshot of difftastic and Rust](img\u002Fwrap_expr.png)\n\n^ Difftastic understands exactly which pieces of syntax have changed,\nand can highlight them in context.\n\n![Screenshot of difftastic and HTML](img\u002Fhtml.png)\n\n^ Difftastic understands when whitespace matters, and when it's just\nan indentation change.\n\n![Screenshot of difftastic and JS](img\u002Freformat.png)\n\n^ Difftastic is not line-oriented. If you reformat your code and it's\nnow split over multiple lines, difftastic will show you what's\nactually changed.\n\n![Screenshot of difftastic and git](img\u002Fgit.png)\n\n^ Difftastic is compatible with git (see [the configuration\ninstructions](https:\u002F\u002Fdifftastic.wilfred.me.uk\u002Fgit.html)), as well as\nmany other version control systems.\n\n## Languages Supported\n\nDifftastic supports over 30 programming languages, see [the\nmanual](https:\u002F\u002Fdifftastic.wilfred.me.uk\u002Flanguages_supported.html) for the full list.\n\nIf a file has an unrecognised extension, difftastic uses a\nline-oriented diff with word highlighting.\n\n## Known Issues\n\nPerformance. Difftastic scales relatively poorly on files with a large\nnumber of changes, and can use a lot of memory.\n\nDisplay. Difftastic has a side-by-side display which usually works well, but can\nbe confusing.\n\nRobustness. Difftastic regularly has releases that fix crashes.\n\n## Non-goals\n\nPatching. Difftastic output is intended for human consumption, and it\ndoes not generate patches that you can apply later. Use `diff` if you\nneed a patch.\n\n(Patch files are also line-oriented, which is too limited for\ndifftastic. Difftastic might find additions and removals on the same\nline, and it tracks the relationship between line numbers in the old\nand new file.)\n\nMerging. AST merging is a hard problem that difftastic does not\naddress. You might be interested in the [mergiraf\ntool](https:\u002F\u002Fmergiraf.org\u002F) (\"merge giraffe\"), which does do AST\nmerging.\n\n## FAQ\n\n### Can I use difftastic with git?\n\nYou can! The difftastic manual [includes instructions for git\nusage](https:\u002F\u002Fdifftastic.wilfred.me.uk\u002Fgit.html). You can also use it\n[with mercurial](https:\u002F\u002Fdifftastic.wilfred.me.uk\u002Fmercurial.html).\n\nIf you're an Emacs user, check out [this blog\npost](https:\u002F\u002Ftsdh.org\u002Fposts\u002F2022-08-01-difftastic-diffing-with-magit.html)\nshowing one way to use difftastic with magit, as well as\n[difftastic.el](https:\u002F\u002Fgithub.com\u002Fpkryger\u002Fdifftastic.el).\n\n### Does difftastic integrate with my favourite tool?\n\nProbably not. Difftastic is young. Consider writing a plugin for your\nfavourite tool, and I will link it in the README!\n\n### What about parse errors?\n\nBy default, difftastic falls back to a line-oriented diff whenever\nparse errors are encountered.\n\nThis is a conservative choice to ensure that difftastic never claims\nthat two syntactically different files are the same.\n\nParse errors can occur if the file uses language features that the\nparser does not understand, if the language relies on a preprocessor\nbefore parsing (e.g. C++), or if the file has genuine syntactic\nmistakes.\n\nIn practice, difftastic virtually always produces a good result when\nthere are a few minor parse errors. Consider allowing a small number\nof parse errors when using difftastic.\n\n```\n$ export DFT_PARSE_ERROR_LIMIT=20\n$ difft foo1.c foo2.c\n```\n\n### Can difftastic help me with merge conflicts?\n\nYes! As of version 0.50, difftastic understands merge conflict markers\n(i.e. `\u003C\u003C\u003C\u003C\u003C\u003C\u003C`, `=======` and `>>>>>>>`).\n\nPass your file with conflicts as a single argument to\ndifftastic. Difftastic will construct the two conflicting files and\ndiff those.\n\n```\n$ difft file_with_conflicts.js\n```\n\n### Can difftastic do merges?\n\nNo. AST merging is a hard problem that difftastic does not address.\n\nAST diffing is a lossy process from the perspective of a text\ndiff. Difftastic will ignore whitespace that isn't syntactically\nsignificant, but merging requires tracking whitespace.\n\nThe [mergiraf](https:\u002F\u002Fmergiraf.org\u002F) tool does offer merges based on\na tree-sitter AST however.\n\n### Can difftastic ignore reordering?\n\nNo. Difftastic always considers order to be important, so diffing\ne.g. `set(1, 2)` and `set(2, 1)` will show changes.\n\nIf you're diffing JSON, consider sorting the keys before passing them\nto difftastic.\n\n```\n$ difft \u003C(jq --sort-keys \u003C file_1.json) \u003C(jq --sort-keys \u003C file_2.json)\n```\n\nSee also [Tricky Cases: Unordered Data\nTypes](https:\u002F\u002Fdifftastic.wilfred.me.uk\u002Ftricky_cases.html#unordered-data-types)\nin the manual.\n\n### Can I use difftastic to check for syntactic changes without diffing?\n\nYes. Difftastic can check if the two files have the same AST, without\ncalculating a diff. This is much faster than normal diffing, and\nuseful for building tools that check for changes.\n\nFor example:\n\n```\n$ difft --check-only --exit-code before.js after.js\n```\n\nThis will set the exit code to 0 if there are no syntactic changes, or\n1 if there are changes found.\n\n### Why aren't colours appearing in my terminal?\n\nDifftastic uses ANSI bright colours by default, but some terminal\nthemes show bright colours as grey. Solarized is a popular theme that\ndoes this.\n\nIf you're a Solarized user, use `export DFT_BACKGROUND=light` to\ndisable bright colours, or try a different terminal colour scheme.\n\n### How does it work?\n\nDifftastic treats structural diffing as a graph problem, and uses\nDijkstra's algorithm.\n\nMy [blog\npost](https:\u002F\u002Fwww.wilfred.me.uk\u002Fblog\u002F2022\u002F09\u002F06\u002Fdifftastic-the-fantastic-diff\u002F)\ndescribes the design, and there is also an [internals section in the\nmanual](https:\u002F\u002Fdifftastic.wilfred.me.uk\u002Fdiffing.html).\n\n## Translation\n\n+ [Chinese](.\u002Ftranslation\u002Fzh-CN\u002FREADME-zh-CN.md)\n\n## License\n\nDifftastic is open source under the MIT license, see LICENSE for more\ndetails.\n\nThis repository also includes tree-sitter parsers by other authors in\nthe `vendored_parsers\u002F` directory. These are a mix of the MIT license and the\nApache license. See `vendored_parsers\u002F*\u002FLICENSE` for more details.\n\nFiles in `sample_files\u002F` are also under the MIT license unless stated\notherwise in their headers.\n","Difftastic 是一款基于语法结构的文件比较工具。它利用Tree-sitter解析器理解多种编程语言（支持超过30种）的语义，从而在比较时能够准确识别并高亮显示实际发生变化的代码片段，而不仅仅是逐行对比文本差异。这使得difftastic特别适用于需要精确了解代码修改内容的场景，如代码审查、版本控制系统的差异展示等。项目采用Rust语言开发，确保了高性能与低资源占用，并且提供了与Git等版本控制系统集成的能力。尽管对于大规模改动的文件处理上可能存在性能瓶颈，但其独特的结构化对比方式为开发者提供了更直观和有用的差异信息。",2,"2026-06-11 03:02:56","top_language"]