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
The parsing around rust does not allow syntax highlighting or proper detection of variables embedded in strings.
As such it seems extremely premature to have this lint active.
I (and many other I'm sure) like to have warnings block merges, but this lint actively makes code worse if a user is using (at least some) LSPs. And blocks hover information on the variable.
I'd suggest that, at the least, this lint be downgraded until LSP, treesitter, and related tooling catch up.
(I also generally question whether pushing for inconsistent string embedding of variables improves readability -- since the lint only applies to some cases.)
Below an example of w/ and w/out lint. Without lint, in the context of LSP tooling, being much easier to read and parse and allowing additional tools (like hover information on type):
Description
re: uninlined_format_args
The parsing around rust does not allow syntax highlighting or proper detection of variables embedded in strings.
As such it seems extremely premature to have this lint active.
I (and many other I'm sure) like to have warnings block merges, but this lint actively makes code worse if a user is using (at least some) LSPs. And blocks hover information on the variable.
I'd suggest that, at the least, this lint be downgraded until LSP, treesitter, and related tooling catch up.
(I also generally question whether pushing for inconsistent string embedding of variables improves readability -- since the lint only applies to some cases.)
Below an example of w/ and w/out lint. Without lint, in the context of LSP tooling, being much easier to read and parse and allowing additional tools (like hover information on type):
Version
Additional Labels
No response
The text was updated successfully, but these errors were encountered: