bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

Fix the comments for libsyntax::parse::parser::parse_sugary_call_expr

Browse source 
The comments on this function date back from when it was used for `for`
expressions in addition to `do` expressions.
This commit is contained in:
Kevin Ballard 2013-12-03 16:55:00 -08:00
parent c8b60a2d9e
commit c00837e90a
1 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

16
src/libsyntax/parse/parser.rs
View file

@ -2530,9 +2530,9 @@ impl Parser {
}
// parse a 'for' or 'do'.
// the 'for' and 'do' expressions parse as calls, but look like
// function calls followed by a closure expression.
// parse a 'do'.
// the 'do' expression parses as a call, but looks like
// a function call followed by a closure expression.
pub fn parse_sugary_call_expr(&self,
lo: BytePos,
keyword: ~str,
@ -2540,12 +2540,12 @@ impl Parser {
ctor: |v: @Expr| -> Expr_)
-> @Expr {
// Parse the callee `foo` in
// for foo || {
// for foo.bar || {
// do foo || {
// do foo.bar || {
// etc, or the portion of the call expression before the lambda in
// for foo() || {
// do foo() || {
// or
// for foo.bar(a) || {
// do foo.bar(a) || {
// Turn on the restriction to stop at | or || so we can parse
// them as the lambda arguments
let e = self.parse_expr_res(RESTRICT_NO_BAR_OR_DOUBLEBAR_OP);
@ -2592,7 +2592,7 @@ impl Parser {
}
_ => {
// There may be other types of expressions that can
// represent the callee in `for` and `do` expressions
// represent the callee in `do` expressions
// but they aren't represented by tests
debug!("sugary call on {:?}", e.node);
self.span_fatal(