Skip to content

rust-mode.el: foo![...] is not highlighted as macros. #13979

New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom
Closed
gifnksm opened this issue May 6, 2014 · 2 comments
Closed

rust-mode.el: foo![...] is not highlighted as macros. #13979

gifnksm opened this issue May 6, 2014 · 2 comments

Comments

@gifnksm
Copy link
Contributor

gifnksm commented May 6, 2014

foo![...] is one of a valid macro invocation syntax, but it is not highlighted correctly with emacs's rust-mode. Other invocation syntax foo!(...) and foo!{..} are highlighted correctly.

rust-mode
@gifnksm gifnksm changed the title rust-mode.el: ![...] is not highlighted as macros. rust-mode.el: foo![...] is not highlighted as macros. May 6, 2014
@gifnksm
Copy link
Contributor Author

gifnksm commented May 6, 2014

cc #8793

@tomjakubowski tomjakubowski mentioned this issue May 13, 2014
Closed
@huonw
Copy link
Member

huonw commented May 13, 2014

Closed by #14087 (via #14164).

@huonw huonw closed this as completed May 13, 2014
flip1995 pushed a commit to flip1995/rust that referenced this issue May 15, 2025
@llogiq
Add new confusing_method_to_numeric_cast lint (rust-lang#13979)
b363499 
Fixes rust-lang/rust-clippy#13973.

I don't think we can make `fn_to_numeric_cast_any` to be emitted in some
special cases. Its category cannot be changed at runtime.

I think in this case, the best might be a specialized new lint so we can
target exactly what we want.

----

changelog: Add new `confusing_method_to_numeric_cast` lint
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gifnksm @huonw