rust/src/test/compile-fail/lint-unconditional-recursion.rs, branch 1.23.0

Stop ignoring expected note/help messages in compiletest suite.

2016-03-17T01:53:58+00:00

Original issue: https://github.com/rust-lang/rust/issues/21195 Relevant PR: https://github.com/rust-lang/rust/pull/30778 Prior to this commit, if a compiletest testcase included the text "HELP:" or "NOTE:" (note the colons), then it would indicate to the compiletest suite that we should verify "help" and "note" expected messages. This commit updates this check to also check "HELP" and "NOTE" (not the absense of colons) so that we always verify "help" and "note" expected messages.

rustc_lint: handle more method calls in unconditional_recursion.

2015-08-03T22:17:56+00:00

lint: default methods must be called on Self to unconditionally recur.

2015-06-29T23:00:54+00:00

This catches the case when a trait defines a default method that calls itself, but on a type that isn't necessarily `Self`, e.g. there's no reason that `T = Self` in the following, so the call isn't necessarily recursive (`T` may override the call). trait Bar { fn method(&self, x: &T) { x.method(x) } } Fixes #26333.

lint: only consider actual calls as unconditional recursion.

2015-06-29T22:59:37+00:00

Specifically, just mentioning the function name as a value is fine, as long as it isn't called, e.g. `fn main() { let _ = main; }`. Closes #21705.

Add a lint to detect unconditional recursion.

2015-01-24T13:21:03+00:00

E.g. `fn foo() { foo() }`, or, more subtlely impl Foo for Box { fn bar(&self) { self.bar(); } } The compiler will warn and point out the points where recursion occurs, if it determines that the function cannot return without calling itself. Closes #17899.