You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use cargo to create a Rust project (ensure rust-analyzer can analyze the code correctly);
Create a function with a mut parameter and notice that the parameter is not italicized;
Create an impl with &mut self and notice that the function is not bold.
Expected behavior
According to the design of One Dark Pro, function parameters should be italicized, but they are currently displayed in regular font.
Screenshots & Example Code
structtemp;#[allow(dead_code)]impltemp{fnshould_bold(&self,should_italic:i32){let _ = should_italic;}fnshould_bold_too(&mutself,should_italic_too:&muti32){//! but it's not boldlet _ = should_italic_too;// but it's not italic}}
Desktop (please complete the following information):
OS: mac, ssh to debian
VSCODE Version v1.95.3
Theme version v3.17.7
Additional context
When rust-analyzer cannot analyze the code, the code display is normal. You can create a temporary page using Command+N and then set it to Rust format. At this point, using the above code, mut is displayed correctly.
It seems that the issue lies in rust-analyzer's handling of mut variables, which adds an underline to mut variables to prompt the developer. One Dark Pro seems unable to display these underlined texts correctly.
The text was updated successfully, but these errors were encountered:
I tried disabling the underline, but it didn’t resolve the issue. Now, I am attempting to adjust other options to make it visually consistent with One Dark Pro.
Describe the bug
After using rust-analyzer, the fontStyle for Rust is displayed incorrectly.
To Reproduce
Steps to reproduce the behavior:
mut
parameter and notice that the parameter is not italicized;impl
with&mut self
and notice that the function is not bold.Expected behavior
According to the design of One Dark Pro, function parameters should be italicized, but they are currently displayed in regular font.
Screenshots & Example Code
Desktop (please complete the following information):
Additional context
When rust-analyzer cannot analyze the code, the code display is normal. You can create a temporary page using Command+N and then set it to Rust format. At this point, using the above code,
mut
is displayed correctly.It seems that the issue lies in rust-analyzer's handling of
mut
variables, which adds an underline tomut
variables to prompt the developer. One Dark Pro seems unable to display these underlined texts correctly.The text was updated successfully, but these errors were encountered: