riff
difftastic
riff | difftastic | |
---|---|---|
8 | 68 | |
487 | 19,575 | |
- | - | |
10.0 | 9.9 | |
7 months ago | 3 days ago | |
Rust | Rust | |
Mozilla Public License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
riff
-
nix-init - Generate Nix packages from URLs with hash prefetching, dependency inference, license detection, and more
Dependency inference for Rust packages using the Riff registry and python projects
-
Generate Nix packages from URLs with hash prefetching and dependency inference
- Dependency inference for Rust packages using the [Riff](https://github.com/DeterminateSystems/riff) registry and python projects
-
An example providing rust toolchain for Linux/macOS using devenv.sh
In this language context specifically, if one wanted to manage their workspace with Nix I would reach for Riff and/or oxalica/rust-overlay first, since they are deliberately more aware of Rust-specific nuance. In the latter's case it has compatibility paths with rustup-toolchain files as well, for allowing your peers who can't or won't adopt Nix to continue to feel like first-class participants in the project. Another alternative I don't have experience with would be nix-community/fenix.
-
devenv: Fast, Declarative, Reproducible, and Composable Developer Environments
Seems to have spiritual overlap with what I understand the goals of Riff to be. Both projects are early stage and not able to cover every language ecosystem yet.
-
An invitation to Rust maintainers from Determinate Systems
No, I wouldn't say that's obvious. Riff doesn't need 100% buy-in from all Rust maintainers because not all Rust projects have external dependencies. But what we've found in our research on the crate ecosystem is that there are particularly busy "nodes" in the dependency graph. Each time a busy "node" with external dependencies adds a few lines to Cargo.toml, that un-breaks a number of downstream project builds. Our internal registry is pretty small but even that has substantially increased the % of projects in which riff run cargo build works without issue. It's an asymptotic approach and we're confident that sufficient awareness could get us pretty darned close.
-
Introducing Riff, a Nix-based tool for automatically providing external dependencies to Rust projects
We currently have a hard-coded [registry](https://github.com/DeterminateSystems/riff/blob/main/registry/registry.json) of some known per-crate dependencies. But the goal is less to hard-code ever more dependencies and more to convince maintainers to explicitly [declare dependencies](https://github.com/determinateSystems/riff#how-to-declare-package-inputs) in their `Cargo.toml` under `package.metadata.riff`. Because Riff uses `cargo metadata` for the entirety of the crate dependency graph, explicit dependency declarations actually benefit downstream crates as well.
difftastic
-
Linus Torvalds adds arbitrary tabs to kernel code
i want a diff tool that shows me exactly which tokens have changed, and which haven't, regardless of how they are laid out.
These already exist: https://github.com/Wilfred/difftastic
when we get that, then we should get even less merge conflicts.
Counterintuitively, that is not the case. AST-merge is a much, much, much, much, much harder problem than AST-diff.
https://github.com/Wilfred/difftastic?tab=readme-ov-file#can...
The fact that diffs can be used to drive a 3-way merge is in fact an accidental property that arises due to the sheer crudeness of the diff format. As soon as you start using more-sophisticated diff formats, solutions to "the diff problem" no longer lead directly to solutions to "the merge problem".
- FLaNK AI Weekly 25 March 2025
-
Difftastic, a structural diff tool that understands syntax
Yes there is an `—-override` option you can use to specify the language in which a file should be parsed.
https://github.com/Wilfred/difftastic/blob/master/CHANGELOG....
-
So You Think You Know Git – Git Tips and Tricks by Scott Chacon
Use the fantastic difftastic instead of git's diff. https://difftastic.wilfred.me.uk/
[alias]
- Difftastic: A structural diff tool that understands syntax
-
SemanticDiff now supports Rust
difftastic provides similar capabilities in a free tool based on treesitter
-
My programming language aware diff for VS Code and GitHub now supports Rust
difftastic? https://github.com/Wilfred/difftastic
-
Prettier $20k Bounty was Claimed
If you're looking for a VS Code extension or a GitHub app, check out https://semanticdiff.com/. I'm a co-founder of this project.
If you prefer a CLI tool, check out https://github.com/Wilfred/difftastic. It supports more languages, but doesn't recognize when code has been replaced by an equivalent version ("invariances"). So it will show some changes (e.g. replacing a character in a string with an escape sequence) even though they are technically equivalent.
-
Pijul: Version-Control Post-Git • Goto 2023
Shameless plug: I've written difftastic[1], a tool that builds ASTs and then does a structural diff of them. You can use it with git too.
It's an incredibly hard problem though, both from a computational complexity point of view, and trying to build a comprehensible UI once you've done the structural AST diff.
[1]: https://github.com/wilfred/difftastic
-
Always leave a trailing comma in Python lists, dicts, tuples
There is a diff tool called difftastic: https://github.com/Wilfred/difftastic
The idea is that it does not show diff based on text change, but on syntastic meaning. For that, it uses tree-sitter.
I think it still shows the trailing comma in the situation as shown in the article, but it's quite different experience than the standard text based diff.
What are some alternatives?
rust-overlay - Pure and reproducible nix overlay of binary distributed rust toolchains
delta - A syntax-highlighting pager for git, diff, and grep output
nixpkgs-pytools - Tools for removing the tedious nature of creating nixpkgs derivations [maintainer=@costrouc]
diffsitter - A tree-sitter based AST difftool to get meaningful semantic diffs
devbox - Instant, easy, and predictable development environments
neogit - An interactive and powerful Git interface for Neovim, inspired by Magit
riff - Riff automatically provides external dependencies for Rust projects, with support for other languages coming soon.
Visual Studio Code - Visual Studio Code
devenv - Pluggable development environments builder that has potential to support any language or framework environment
gumtree - An awesome code differencing tool
riff - A diff filter highlighting which line parts have changed
tree-sitter-cpp - C++ grammar for tree-sitter