Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rust-analyzer.toml #18943

Open
Mirkopoj opened this issue Jan 15, 2025 · 1 comment
Open

rust-analyzer.toml #18943

Mirkopoj opened this issue Jan 15, 2025 · 1 comment
Labels
C-support Category: support questions

Comments

@Mirkopoj
Copy link

I have the following rust-analyzer.toml

[cargo]
allTargets = false
target =  "riscv32imc-unknown-none-elf"

I added this because I was getting a wrong diagnosis.
Adding this to my editor's config solves it, but this is only relevant to this particular project.
As I wanted to not have this error show up while editing, but this solution only makes sense in this project, I added a rust-analyzer.toml file next to my Cargo.toml and removed those configs from my editor's configuration.
After doing this rust-analyzer went back to showing the improper diagnosis.

Are this configs not supported on rust-analyzer.toml?
How should I manually run rust-analyzer to check if this is an issue with my editor instead?
Is there a way to check what configuration is loaded on a given rust-analyzer instance?

Thanks in advance, great tool!!

@Mirkopoj Mirkopoj added the C-support Category: support questions label Jan 15, 2025
@Veykril
Copy link
Member

Veykril commented Jan 16, 2025

They are supported, but the rust-analyzer.toml loading is severely broken right now unfortunately and fixing that is blocked on us fixing our file system infrastructure so this will take a bit unfortunately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-support Category: support questions
Projects
None yet
Development

No branches or pull requests

2 participants