<'static> || doesn't work #11210

huonw · 2013-12-30T06:53:54Z

fn main() {
    let _: 'static ||;
    let _: <'static> ||;
}

closure-static.rs:3:12: 3:19 error: illegal lifetime parameter name: `static`
closure-static.rs:3     let _: <'static> ||;
                                ^~~~~~~

The text was updated successfully, but these errors were encountered:

alexcrichton · 2013-12-30T17:44:44Z

Nominating.

pnkfelix · 2014-01-09T18:44:44Z

Probable dupe of #11209.

pnkfelix · 2014-01-09T18:45:06Z

(denominating since fix for #11209 should fix this too.)

In summary these are some example transitions this change makes: 'a || => ||: 'a proc:Send() => proc():Send The intended syntax for closures is to put the lifetime bound not at the front but rather in the list of bounds. Currently there is no official support in the AST for bounds that are not 'static, so this case is currently specially handled in the parser to desugar to what the AST is expecting. Additionally, this moves the bounds on procedures to the correct position, which is after the argument list. The current grammar for closures and procedures is: procedure := 'proc' [ '<' lifetime-list '>' ] '(' arg-list ')' [ ':' bound-list ] [ '->' type ] closure := [ 'unsafe' ] ['<' lifetime-list '>' ] '|' arg-list '|' [ ':' bound-list ] [ '->' type ] lifetime-list := lifetime | lifetime ',' lifetime-list arg-list := ident ':' type | ident ':' type ',' arg-list bound-list := bound | bound '+' bound-list bound := path | lifetime This does not currently handle the << ambiguity in `Option<<'a>||>`, I am deferring that to a later patch. Additionally, this removes the support for the obsolete syntaxes of ~fn and &fn. Closes rust-lang#10553 Closes rust-lang#10767 Closes rust-lang#11209 Closes rust-lang#11210 Closes rust-lang#11211

In summary these are some example transitions this change makes: 'a || => ||: 'a proc:Send() => proc():Send The intended syntax for closures is to put the lifetime bound not at the front but rather in the list of bounds. Currently there is no official support in the AST for bounds that are not 'static, so this case is currently specially handled in the parser to desugar to what the AST is expecting. Additionally, this moves the bounds on procedures to the correct position, which is after the argument list. The current grammar for closures and procedures is: procedure := 'proc' [ '<' lifetime-list '>' ] '(' arg-list ')' [ ':' bound-list ] [ '->' type ] closure := [ 'unsafe' ] ['<' lifetime-list '>' ] '|' arg-list '|' [ ':' bound-list ] [ '->' type ] lifetime-list := lifetime | lifetime ',' lifetime-list arg-list := ident ':' type | ident ':' type ',' arg-list bound-list := bound | bound '+' bound-list bound := path | lifetime This does not currently handle the << ambiguity in `Option<<'a>||>`, I am deferring that to a later patch. Additionally, this removes the support for the obsolete syntaxes of ~fn and &fn. Closes #10553 Closes #10767 Closes #11209 Closes #11210 Closes #11211

new lint: [`readonly_write_lock`] Closes rust-lang#8555 A new lint that catches `RwLock::write` calls to acquire a write lock only to read from it and not actually do any writes (mutations). changelog: new lint: [`readonly_write_lock`]

alexcrichton mentioned this issue Apr 2, 2014

syntax: Tweak parsing lifetime bounds on closures #13268

Merged

alexcrichton closed this as completed in d1c584e Apr 6, 2014

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

<'static> || doesn't work #11210

<'static> || doesn't work #11210

huonw commented Dec 30, 2013

alexcrichton commented Dec 30, 2013

pnkfelix commented Jan 9, 2014

pnkfelix commented Jan 9, 2014

<'static> || doesn't work #11210

<'static> || doesn't work #11210

Comments

huonw commented Dec 30, 2013

alexcrichton commented Dec 30, 2013

pnkfelix commented Jan 9, 2014

pnkfelix commented Jan 9, 2014