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
…ed, r=camsteffen
Don't trigger semicolon_if_nothing_returned in expanded code
Fixesrust-lang#7768
Before, this lint didn't trigger on macros. With rust-lang#88175
this isn't enough anymore. In this PR a `WhileLoop` desugaring kind was
introduced. This overrides the span of expanded expressions when
lowering the while loop. So if a while loop is in a macro, the
expressions that it expands to are no longer marked with
`ExpnKind::Macro`, but with `ExpnKind::Desugaring`. In general, this is
the correct behavior and the same that is done for `ForLoop`s. It just
tripped up this lint.
r? `@camsteffen`
changelog: [`semicolon_if_nothing_returned`]: Fix regression on macros containing while loops
I feel it would make everybody much more productive if the build system was well documented. The need for people to know more about it is clearly shown by people posting stuff like this http://www.reddit.com/r/rust/comments/1fz5xu/public_service_announcement_make_checkstage1std/ .
All the details of the build system should be well documented including how to build, test, and benchmark Rust at all stages.
The text was updated successfully, but these errors were encountered: