Skip to content

Struct tuples cause IntelliSense problems on VSCode #5429

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

Closed
charlespeary opened this issue Jul 18, 2020 · 1 comment
Closed

Struct tuples cause IntelliSense problems on VSCode #5429

charlespeary opened this issue Jul 18, 2020 · 1 comment
Labels
S-actionable Someone could pick this issue up and work on it right now

Comments

@charlespeary
Copy link

Hello!

VSCode version: 1.46.1
Rust analyzer plugin version: 0.2.240
Active toolchain: nightly-x86_64-unknown-linux-gnu
Code: https://gist.github.com/Sniadekk/a7ee128f6f27805f96eccf26a8efdaec
Screenshots of the problem: https://imgur.com/a/WJCDsgA

I stumbled upon a bug while solving one of the Advent of Code problems.
The Object tuple struct contains String and Option<Box<Object>> inside.
While working on the tree_size function and trying to access the node.1 I have the same IntelliSense as with the node.0 which is a String, but there should be tips for the Option type instead.
Seems like the error isn't gone after I reload the VSCode.

I will be more than happy to provide more information to you to reproduce the bug.

Have a great day and thank you for your work.

@charlespeary charlespeary changed the title Problem with IntelliSense on struct tuples on VSCode Struct tuples cause IntelliSense problems on VSCode Jul 23, 2020
@flodiebold flodiebold added the S-actionable Someone could pick this issue up and work on it right now label Dec 21, 2020
@Veykril
Copy link
Member

Veykril commented Nov 11, 2022

Caused by #1109 so closing as resolving that willr esolve this issue as well.

@Veykril Veykril closed this as completed Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-actionable Someone could pick this issue up and work on it right now
Projects
None yet
Development

No branches or pull requests

3 participants