pacak

I'm definitely interested, will try to check it out soon. As for where it goes - might switch to it in 0.10. Need to check a few things. 0.10 is...

> I added a compile time error for that in the proc macro for the basic pitfall since it also annoyed me :) I didn't do it because it covers...

> Sadly [scraped-examples](https://doc.rust-lang.org/rustdoc/scraped-examples.html) is still unstable. This is actually fine and I'm already using it. You can just pass whatever unstable flags `docs.rs` will build it with. Problem is that...

Encountered a similar problem with new files in `examples/` and `neovim`. With the stuff I'm trying to achieve restarting `rust-analyzer` doesn't work, but creating a new file before switching to...

I'm using `rustc_demangle` [1], whatever it supports works. Nothing specific comes to mind. Try passing `-vvv` and see what file it tries to work with and check if symbols are...

Same as more tickets - blocked on `cargo`: https://github.com/rust-lang/cargo/issues/13672

Actually no, it just randomly closes some, but not all folds, that I open with `zo`. Looks like it somehow related to `foldlevel=0` I'm getting every once in a while....

I guess it's this bit. ```lua -- Using ufo provider need remap `zR` and `zM`. If Neovim is 0.6.1, remap yourself vim.keymap.set('n', 'zR', require('ufo').openAllFolds) vim.keymap.set('n', 'zM', require('ufo').closeAllFolds) ``` It's not...

There's `--disasm` option (needs "disasm" feature) that would disassemble the actual binary instead of asking for `rustc` to produce annotated `.s` file. Difference can come from any LTO you might...

Not much I can do about LTO apart from complaining or automatically falling back to `--disasm`. "disasm" feature is the default behavior since the output is a bit less readable...