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

RFC#3416 failing #17918

Closed
amab8901 opened this issue Aug 17, 2024 · 2 comments
Closed

RFC#3416 failing #17918

amab8901 opened this issue Aug 17, 2024 · 2 comments
Labels
C-support Category: support questions

Comments

@amab8901
Copy link

amab8901 commented Aug 17, 2024

rust-analyzer version:
rust-analyzer version: 0.3.2070-standalone [/home/user/.vscode-oss/extensions/rust-lang.rust-analyzer-0.3.2070-linux-x64/server/rust-analyzer]

rustc version:
rustc 1.80.1 (3f5fd8dd4 2024-08-06)

editor or extension:
VSCode, [email protected]

code snippet to reproduce:

Literally just create a blank project and copy-paste the following in Cargo.toml:

[features]
foo = { enables = [] }

It should work according to this RFC.

But instead it produces this error:

2024-08-17T18:58:44.397863Z ERROR Flycheck failed to run the following command: CommandHandle { program: "/home/user/.cargo/bin/cargo", arguments: ["check", "--workspace", "--message-format=json-diagnostic-rendered-ansi", "--manifest-path", "/home/user/src/nice/Cargo.toml", "--keep-going", "--all-targets"], current_dir: Some("/home/user/src/nice") }, error=Cargo watcher failed, the command produced no valid metadata (exit code: ExitStatus(unix_wait_status(25856))):
error: invalid type: map, expected a sequence
  --> Cargo.toml:10:7
   |
10 | foo = { enables = [] }
   |       ^^^^^^^^^^^^^^^^
   |

@amab8901 amab8901 added the C-bug Category: bug label Aug 17, 2024
@lnicola
Copy link
Member

lnicola commented Aug 17, 2024

Is that really implemented? cargo check seems to reject it.

Just because an RFC is accepted, it doesn't mean it's implemented and stabilized.

@lnicola lnicola added C-support Category: support questions and removed C-bug Category: bug labels Aug 17, 2024
@amab8901
Copy link
Author

oh! yeah makes sense. I realized it's not implemented.

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