Upstream issues: fixes and features in other tools that would benefit Pavex
This is a meta-issue to keep track of feature requests/bugs in other projects that affect Pavex.
-
IDE experience:
- Auto-completion and go-to-definition inside the f! macro
- https://github.com/rust-lang/rust-analyzer/issues/14999
- Blocked on https://github.com/rust-lang/rust/issues/66079
- https://github.com/intellij-rust/intellij-rust/issues/10543)
- https://github.com/rust-lang/rust-analyzer/issues/14999
- Auto-completion and go-to-definition inside the f! macro
-
Pavex's CLI performance:
- https://github.com/rust-lang/cargo/issues/13283
Heads up: We might be changing how rustdoc-json handles paths in a way that might break you. Details are in https://github.com/rust-lang/rust/pull/134880. If you use the Crate::paths field you should be fine, but if you rely on Path::name for resolving cross-crate paths then this will break you. Please comment on that PR if moving to Crate::paths doesn't work somehow. Thanks!
I have a feeling this might be an issue, but I have to go and review the relevant code paths. I'll try to carve some time tomorrow. Thanks for the heads up!