rust/tests/ui/feature-gates/feature-gate-unboxed-closures-method-calls.rs

#![allow(dead_code)]

fn foo<F: Fn()>(mut f: F) {
    f.call(()); //~ ERROR use of unstable library feature `fn_traits`
    f.call_mut(()); //~ ERROR use of unstable library feature `fn_traits`
    f.call_once(()); //~ ERROR use of unstable library feature `fn_traits`
}

fn main() {}
Feature-gate explicit unboxed closure method calls & manual impls, detect UFCS drop and allow UFCS methods to have explicit type parameters. Work towards #18875. Since code could previously call the methods & implement the traits manually, this is a [breaking-change] Closes #19586. Closes #19375. 2014-12-05 15:53:30 -08:00			`#![allow(dead_code)]`

Feature-gate `<>` syntax used with `Fn`. Fixes #18875. 2015-01-10 08:38:51 -05:00			`fn foo<F: Fn()>(mut f: F) {`
use backticks instead of single quotes when reporting "use of unstable library feature" This is consistent with all other diagnostics I could find containing features and enables the use of `DiagSymbolList` for generalizing diagnostics for unstable library features to multiple features. 2024-11-02 16:10:24 -07:00			f.call(()); //~ ERROR use of unstable library feature `fn_traits`
			f.call_mut(()); //~ ERROR use of unstable library feature `fn_traits`
			f.call_once(()); //~ ERROR use of unstable library feature `fn_traits`
Feature-gate explicit unboxed closure method calls & manual impls, detect UFCS drop and allow UFCS methods to have explicit type parameters. Work towards #18875. Since code could previously call the methods & implement the traits manually, this is a [breaking-change] Closes #19586. Closes #19375. 2014-12-05 15:53:30 -08:00			`}`

			`fn main() {}`