@sunshowers6 Maybe a bit early, but are these features something that could be "upstreamed" into cargo test? Would be excellent to have them by default.
@CecileTonglet I quite like the "Not rocket science rule" as per https://t.co/uKR0JEooYn . Definitely confusing to explain to people though.
Maybe "the main branch has changed in an incompatible way since you raised the PR"?
We've been using this at work, and now we get to share it with the world: `apple_rules_lint` a lightweight linting framework for @bazelbuild. https://t.co/yZ7zbQL56H
What does it do? It allows ruleset authors to plugin lint checks into your builds.
Let's take a tourโฆ
@Samuel_Zanca Cool! I've been thinking of trying the Nix package manager for doing this stuff, would be nice to have one package manager that can also do things like link dotfiles, and runs on macOS and Linux.
@15214framework Oh cool, I've been trying to do the same for the last few days. Have you been looking at making things play better with cargo-raze or something else? I've found -sys crates with chunky https://t.co/XYKiPpZz7Q files the most annoying FWIW.
@Erstejahre It's a workaround not a solution, but useful in general to increase this limit for things like `entr` or `cargo-watch`. I use: https://t.co/oit6FjaGn6
@spacekookie There are some great examples in the fzf wiki for this (https://t.co/i0HPW65D2H). I ended up with Ctrl-G+{f,b,t,h,r} for git searching files,branches,tags,hashes,remotes , and it's so useful (https://t.co/Ry2N1L3vCW). `git add ^gf`, `git fix ^gh` etc...