os-rust/tests/ui/issues/issue-3021-b.rs

fn siphash(k0 : u64) {

    struct SipHash {
        v0: u64,
    }

    impl SipHash {
        pub fn reset(&mut self) {
           self.v0 = k0 ^ 0x736f6d6570736575; //~ ERROR can't capture dynamic environment
        }
    }
}

fn main() {}
Correctly forbid upvars in nested impls, traits and classes Previously, resolve was allowing impls, traits or classes that were nested within a fn to refer to upvars, as well as referring to type parameters bound by the fn. Fixing this required adding a new kind of def: def_typaram_binder, which can refer to any of an impl, trait or class that has bound ty params. resolve uses this to enforce that methods can refer to their parent item's type parameters, but not to outer items' type parameters; other stages ignore it. I also made sure that impl, trait and class methods get checked inside a MethodRibKind thing so as to forbid upvars, and changed the definition of MethodRibKind so that its second argument is an optional node_id (so that required trait method signatures can be checked with a MethodRibKind as well). 2012-07-26 14:04:03 -07:00			`fn siphash(k0 : u64) {`

make non_camel_case_types an early lint 2018-12-16 22:21:47 -05:00			`struct SipHash {`
test: De-mut the test suite. rs=demuting 2013-02-22 16:08:16 -08:00			`v0: u64,`
Convert class methods to impl methods. Stop parsing class methods 2012-09-07 19:04:40 -07:00			`}`

make non_camel_case_types an early lint 2018-12-16 22:21:47 -05:00			`impl SipHash {`
Remove all uses of `pub impl`. rs=style 2013-05-31 15:17:22 -07:00			`pub fn reset(&mut self) {`
Improve the attempted dynamic environment-capture error message 2013-07-01 23:17:43 +05:30			`self.v0 = k0 ^ 0x736f6d6570736575; //~ ERROR can't capture dynamic environment`
Correctly forbid upvars in nested impls, traits and classes Previously, resolve was allowing impls, traits or classes that were nested within a fn to refer to upvars, as well as referring to type parameters bound by the fn. Fixing this required adding a new kind of def: def_typaram_binder, which can refer to any of an impl, trait or class that has bound ty params. resolve uses this to enforce that methods can refer to their parent item's type parameters, but not to outer items' type parameters; other stages ignore it. I also made sure that impl, trait and class methods get checked inside a MethodRibKind thing so as to forbid upvars, and changed the definition of MethodRibKind so that its second argument is an optional node_id (so that required trait method signatures can be checked with a MethodRibKind as well). 2012-07-26 14:04:03 -07:00			`}`
			`}`
			`}`

			`fn main() {}`