about summary refs log tree commit diff
path: root/src/comp/syntax/parse/parser.rs
AgeCommit message (Collapse)AuthorLines
2012-01-25rustc: Allow attributes on enum variants. Closes #1663Brian Anderson-1/+5
2012-01-25Correctly increment sess.byte_pos.Kevin Atkinson-4/+4
2012-01-25Keep source file around after parsing.Kevin Atkinson-9/+10
Specifically box the string (to avoid unnecessary copies) and store it in codemap::filemap. Remove the hack in driver::diagnostic that rereads the source from the file and instead just get the source from the filemap. (This commit is also a prerequisite for issue #1612)
2012-01-25Implement implicit self type parameters for ifacesMarijn Haverbeke-2/+3
Closes #1661
2012-01-25Rename tag to enum throughout the compilerMarijn Haverbeke-15/+15
This should reduce confusion of people trying to read the code.
2012-01-25Repair zero-variant tagsMarijn Haverbeke-51/+24
The parser no longer parsed them.
2012-01-24rustc: Split diagnostics into "span diagnostics" and "diagnostics".Patrick Walton-10/+11
The former contain a codemap (which is per-crate), and the latter don't. This will be useful in order to allow more than one crate to be compiled in one run of the compiler.
2012-01-24comp: Fix syntax error in parserBrian Anderson-1/+1
2012-01-23Added to bad_expr_word_table reserved wordsJoshua Clark-2/+3
2012-01-23s/block()/fn()/gNiko Matsakis-14/+8
2012-01-23Don't reset the chpos/byte_pos to 0 in new_parser_from_source_str.Kevin Atkinson-11/+23
This correctly fixes issue #1362. chpos/byte_pos are now the offsets within a particular file, but rather the offsets within a virtual file with is formed by combing all of the modules within a crate. Thus, resetting them to 0 causes an overlap and hence, bogus source locations. Fix #1362 by moving chpos/byte_pos to parse_sess so that new_parser_from_source_str has access to them and hence can chose an initial value that is not already been used in the crate. Note that the trigger for bug 1361 was that syntax/ext/expand.rs calls parse_expr_from_source_str (which calls new_parser_from_source_str) using the same codemap as the current crate (and hence causing overlap with files in the crate as new_parser_from_source_str resets the chpos/byte_pos to 0).
2012-01-23Export all enum variants by default; new syntax for selectively exporting ↵Tim Chevalier-11/+12
variants See issue 1426 for details. Now, the semantics of "export t;" where t is a tag are to export all of t's variants as well. "export t{};" exports t but not its variants, while "export t{a, b, c};" exports only variants a, b, c of t. To do: - documentation - there's currently no checking that a, b, c are actually variants of t in the above example - there's also no checking that t is an enum type, in the second two examples above - change the modules listed in issue 1426 that should have the old export semantics to use the t{} syntax I deleted the test export-no-tag-variants since we're doing the opposite now, and other tests cover the same behavior.
2012-01-20WIP on issue 1426 (exporting all tags)Tim Chevalier-4/+28
Support Lenny222's proposed syntax for exporting a tag without its variants, or selected tags from a variant, in the AST and parser. No support further down the line yet. Tests are xfailed.
2012-01-19Additional ; to , changes, disable "tag" and ";" in parser. Close #1430. ↵Graydon Hoare-1/+1
Close #1428.
2012-01-19rustc: Stop parsing "tag"Patrick Walton-2/+2
2012-01-19rustc: ";" to "," in enumsPatrick Walton-6/+6
2012-01-19rustc: "tag" -> "enum"Patrick Walton-7/+7
2012-01-19Rename fn*() to fn() as originally planned.Niko Matsakis-7/+9
2012-01-19treat fn*() as fn&()Niko Matsakis-8/+2
This is not my ideal way of going about things. I'd prefer not to have expressions typed as fn*(), for example, but I couldn't get that to work together with inferring the modes of arguments and other corner cases.
2012-01-19Remove support for the '.' after a nullary tag in a patternTim Chevalier-4/+0
(Commit also includes lots of changes to remove '.'s that a git merge messed up, or else it was monkeys.)
2012-01-18Remove '.' after nullary tags in patternsTim Chevalier-64/+64
Does what it says on the tin. The next commit will remove support for this syntax.
2012-01-18Allow any alternative (not just a block) to follow a nullary tag patternTim Chevalier-3/+1
2012-01-18allow dotless nullary patterns inside or-patternsTim Chevalier-1/+2
2012-01-18Another minor parser fix for nullary-tag patternsTim Chevalier-1/+1
2012-01-18Allow nullary tag names to be qualifiedTim Chevalier-3/+2
2012-01-18rustc: Assert that the parser doesn't assign node id 0Brian Anderson-0/+2
It is reserved for indicating the crate, but doesn't exist in the AST
2012-01-18rustc: Accept commas to separate tag variantsPatrick Walton-3/+12
2012-01-17Allow omission of the '.' after nullary tag patternsTim Chevalier-6/+23
This commit allows patterns like: alt x { some(_) { ... } none { } } without the '.' after none. The parser suspends judgment about whether a bare ident is a tag or a new bound variable; instead, the resolver disambiguates. This means that any code after resolution that pattern-matches on patterns needs to call pat_util::normalize_pat, which consults an environment to do this disambiguation. In addition, local variables are no longer allowed to shadow tag names, so this required changing some code (e.g. renaming variables named "mut", and renaming ast::sub to subtract). The parser currently accepts patterns with and without the '.'. Once the compiler and libraries are changed, it will no longer accept the '.'.
2012-01-16Don't evaluate discriminator value constants when parsing.Kevin Atkinson-27/+2
Remove disr_val from ast::variant_ and always use ty::variant_info when the value is needed. Move what was done during parsing into other passes, primary typeck.rs. This move also correctly type checks the disr. value expression; thus, fixing rustc --pretty=typed when disr. values are used.
2012-01-15rustc: Parse fn inner attributes. Closes #1506Brian Anderson-29/+96
2012-01-15rustc: Extract comman parts of view parsingBrian Anderson-7/+13
2012-01-13rustc: Replace the lexer's error handling with diagnostic implBrian Anderson-2/+4
2012-01-13rustc: Replace parser's error handling with diagnostic implBrian Anderson-9/+10
2012-01-13rustc: Extract driver::diagnostic from syntax::codemapBrian Anderson-4/+5
2012-01-13rustc: Refactor codemap::emit_* functionsBrian Anderson-5/+4
A codemap is only needed when we have a span so put them both into the option.
2012-01-13distinguish "any closure" and "stack closure" (block)Niko Matsakis-10/+10
2012-01-13make blocks fn& and fn stand for "any closure"Niko Matsakis-14/+17
2012-01-13deprecate fn exprs and the fn() type, preferring fn@ and native fnNiko Matsakis-2/+13
2012-01-13Obj system? What obj system?Marijn Haverbeke-77/+7
Removes the obj system from the compiler. Closes #1484
2012-01-13Convert the objects used in the lexer and parser to records + implsMarijn Haverbeke-343/+311
2012-01-12make parser disambiguate fn~ at top level correctlyNiko Matsakis-1/+12
2012-01-12Cleanups to previous commits for issue #1393.Kevin Atkinson-2/+2
2012-01-10Fold and re-evaluate expr in tag discriminant.Graydon Hoare-1/+1
2012-01-10Support explicit discriminant numbers on tag variants.Kevin Atkinson-2/+41
Addresses issue #1393. For now disallow disr. values unless all variants use nullary contractors (i.e. "enum-like"). Disr. values are now encoded in the crate metadata, but only when it will differ from the inferred value based on the order.
2012-01-10rustc: Accept "enum" in addition to "tag"Patrick Walton-2/+3
2012-01-10replace lambda with fn@Niko Matsakis-1/+5
2012-01-10rename sendfn to fn~, lambda to fn@Niko Matsakis-7/+10
2012-01-09Remove support for 'when' in alt-patterns from parserAustin Seipp-5/+1
Issue #1396
2012-01-09Change all uses of 'when' in alt-patterns to 'if'Austin Seipp-3/+3
Issue #1396
2012-01-09Remove proto_sugar and 'lambda' as keyword, commit to fn@.Graydon Hoare-6/+6
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-26 06:43:58 +0000