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
lifthrasiir opened this issue
Feb 11, 2013
· 0 comments
Labels
A-parserArea: The parsing of Rust source code to an ASTE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
A line filled with only /s is occasionally used as a separator in the code. Rust currently parses it as a doc comment which causes unwanted headaches, as shown below:
////////////////////////////////////////
// common macros
macro_rules! foo( ... ) // error: macro_rules! do not support #[doc = ...]
macro_rules! bar( ... )
While such separators should be avoided in favor of the module system, it is still useful for logically splitting large functions for instance. Also related to #4106.
The text was updated successfully, but these errors were encountered:
…hism
This is a natural extension of #4887, and handles the following three cases:
~~~~
a line with only /s
////////////////////////////////////////////
a line with only /s followed by whitespace
////////////////////////////////////////////
a block comment with only *s between two /s
/********************************/
~~~~
Rework use_self impl based on ty::Ty comparison rust-lang#3410 | Take 2
This builds on top of rust-lang#5531
I already reviewed and approved the commits by `@montrivo.` So only the review of my commits should be necessary.
I would also appreciate your review `@montrivo,` since you are familiar with the challenges here.
Fixesrust-lang#3410 and Fixesrust-lang#4143 (same problem)
Fixesrust-lang#2843Fixesrust-lang#3859Fixesrust-lang#4734 and fixesrust-lang#6221Fixesrust-lang#4305Fixesrust-lang#5078 (even at expression level now 🎉)
Fixesrust-lang#3881 and Fixesrust-lang#4887 (same problem)
Fixesrust-lang#3909
Not yet: rust-lang#4140 (test added)
All the credit for the fixes goes to `@montrivo.` I only refactored and copy and pasted his code.
changelog: rewrite [`use_self`] lint and fix multiple (8) FPs. One to go.
A-parserArea: The parsing of Rust source code to an ASTE-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
A line filled with only
/
s is occasionally used as a separator in the code. Rust currently parses it as a doc comment which causes unwanted headaches, as shown below:While such separators should be avoided in favor of the module system, it is still useful for logically splitting large functions for instance. Also related to #4106.
The text was updated successfully, but these errors were encountered: