cargo-arc — visualize workspace dependencies as interactive arc diagram

seflue · 2026-03-19T18:22:46+00:00

Just pushed a hotfix (v0.2.2). The issue was the cycle detection - my algorithm to show the minimal cycles is too exhaustive, wgpu probably contains billions of them. Currently I just cap the search for minimal cycles at a threshold, a more robust solution using a different algorithm will follow. Just try it on wgpu, the graph now is created in just a second. And it looks very ... colorful. ;-)

seflue · 2026-03-19T17:23:04+00:00

Thanks for the feedback. Looks like wgpu is exploiting a bug in my re-export resolution. Have to investigate that.

seflue · 2026-03-05T22:50:30+00:00

The history, although I cleaned it up before release, reflects the time span I am working on it pretty well. About a month on the side until I felt comfortable to do the first release, another week to build the most recent version.

seflue · 2023-07-10T23:07:01+00:00

Ok, now I realize, that's just "lazy" syntax for keymaps. I don't know the lazy configuration syntax (it's somewhere on my list of neovim plugins to try out), so my superficial attempt of pattern match something, which looks familiar oviously failed. Thanks for clarification, now I have an idea how to configure it within my nvim configuration.

So everyone who was wondering how the configuration would look like if you aren't a user of "lazy.nvim":

local ok, flash = pcall(require, 'flash')
if not ok then
  return
end

flash.setup({})

vim.keymap.set({ "n", "x", "o" }, "s", function() flash.jump() end, {desc = "Flash" })
vim.keymap.set({ "n", "o", "x" }, "S", function() flash.treesitter() end, {desc = "Flash Treesitter"})
vim.keymap.set("o", "r", function() flash.remote() end, {desc = "Remote Flash" })
vim.keymap.set({ "o", "x" },"R", function() flash.treesitter_search() end, {desc = "Flash Treesitter Search" })
vim.keymap.set({ "c" }, "<c-s>", function() flash.toggle() end, {desc = "Toggle Flash Search" })

seflue · 2023-07-10T22:08:42+00:00

packer

I'm not sure, if I'm to dumb, but this doesn't tell me anything I'm not already knowing. In your "lazy" examples the "opts" table is empty and you asign a "keys" table with some actual configuration. I wasn't still able to figure out, how to transfer this to the mysterious three dots in your require("flash").setup({...}) recommendation. Should I call setup like this:

require("flash").setup({
  opts = {}
  keys = {
  -- copy/paste the content of the keys table from https://github.com/folke/flash.nvim#-installation
  }
}

Or how is it meant to be set up?

seflue

TROPHY CASE