rust/src/tools/rust-analyzer/lib
David Faure 34fe0cecf4 internal: fix gdb pretty printer when using Repr::Static
I missed a ["__0"] to access the str in the Static case.

Also, simplify the code to rely on the pretty printer for str
rather than accessing data_ptr/length directly. This makes it
more robust against changes in str.

Output before: "<SmolStr Static error: There is no member named data_ptr.>"
Output after: "preferred-width"
2025-11-30 10:35:07 +01:00
..
la-arena edition = "2024" 2025-03-15 21:32:01 +01:00
line-index chore: Bump dependencies 2025-03-23 08:46:10 +01:00
lsp-server Merge pull request #20393 from rust-lang/veykril/push-urpzrkwpkmxw 2025-08-06 16:12:58 +00:00
smol_str internal: fix gdb pretty printer when using Repr::Static 2025-11-30 10:35:07 +01:00
text-size Merge pull request #21002 from Veykril/veykril/push-nztxvpnntmrx 2025-11-15 09:17:16 +02:00
ungrammar Fix elided lifetime 2025-11-18 14:06:52 +02:00
README.md Allow rust files to be used linkedProjects 2024-04-21 16:26:55 +02:00

lib

Crates in this directory are published to crates.io and obey semver.

They could live in a separate repo, but we want to experiment with a monorepo setup.

We use these crates from crates.io, not the local copies because we want to ensure that rust-analyzer works with the versions that are published. This means if you add a new API to these crates, you need to release a new version to crates.io before you can use that API in rust-analyzer.

To release new versions of these packages, change their version in Cargo.toml. Once your PR is merged into master a workflow will automatically publish the new version to crates.io.

While prototyping, the local versions can be used by uncommenting the relevant lines in the [patch.'crates-io'] section in Cargo.toml