about summary refs log tree commit diff
path: root/src/comp/syntax/print/pprust.rs
AgeCommit message (Collapse)AuthorLines
2011-09-02Rename ty_istr to ty_str. Issue #855Brian Anderson-1/+1
2011-09-02Reformat. Issue #855Brian Anderson-294/+259
2011-09-01Remove lots of estr code from rustc. Issue #855Brian Anderson-2/+1
2011-09-01Rename std::istr to std::str. Issue #855Brian Anderson-10/+10
2011-09-01Parse "",str as istrs. Pretty print istrs as "",str. Issue #855Brian Anderson-8/+1
2011-09-01Remove std::str. Issue #855Brian Anderson-1/+0
2011-08-27Convert rustc::syntax::ast_util to istrs. Issue #855Brian Anderson-6/+6
2011-08-27Convert pretty-printer to istrs. Issue #855Brian Anderson-299/+304
2011-08-27Convert lexer to istrs. Issue #855Brian Anderson-8/+13
2011-08-27Convert rest of the AST to istrs. Issue #855Brian Anderson-6/+10
2011-08-27Convert ast::ident to istr. Issue #855Brian Anderson-45/+59
2011-08-27Convert std::io to istrs. Issue #855Brian Anderson-3/+3
2011-08-27Convert std::int to istrs. Issue #855Brian Anderson-2/+2
2011-08-27Convert std::uint to istrs. Issue #855Brian Anderson-2/+3
2011-08-25Support unchecked blocksTim Chevalier-0/+5
This patch supports the syntax unchecked { ... } to disable purity checking within a block. Presumably it will only be used within a declared "pure fn". However, there is no checking that it doesn't occur elsewhere, and it would be harmless for it to do so. I went with Lindsey's suggestion for the syntax, but it's subject to change. This allows you to write code that uses predicates that call arbitrary Rust functions, but you must declare your intentions by wrapping it in an unchecked { ... } block. The test case run-pass/unchecked-predicates.rs demonstrates how to do that.
2011-08-24Change "pred" to "pure fn" (but still accept "pred")Tim Chevalier-1/+1
This is part 1 of changing the "pred" keyword to "pure fn". Right now, the compiler accepts both "pred" and "pure fn".
2011-08-23Fix pretty-printing of istr literals. Issue #855Brian Anderson-1/+11
2011-08-22Move functions from syntax::ast to syntax::ast_utilBrian Anderson-6/+7
This leaves syntax::ast just defining the AST, which strikes me as somewhat nicer
2011-08-22Implement pattern guardsMarijn Haverbeke-0/+8
The syntax is alt x { mypat where mycond { ... } } The condition may refer to any of the variables bound by the pattern. When a guard fails, pattern-matching continues with the next pattern. Closes #857
2011-08-20ReformatBrian Anderson-167/+133
This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[]
2011-08-19Pretty-print new index syntaxBrian Anderson-3/+2
2011-08-19Pretty-print constrained types correctlyBrian Anderson-1/+6
2011-08-19Pretty-print parens around more things that need disambiguationBrian Anderson-7/+17
Ridiculous stuff like (ret 0) == (log "error")
2011-08-19Teach the pretty-printer to disambiguate 'if ret { }' et. alBrian Anderson-3/+15
2011-08-19Do better at preserving blank lines during pretty-printingBrian Anderson-1/+5
2011-08-19Don't pretty-print extra blank lines after anon object methodsBrian Anderson-2/+5
2011-08-18Don't pretty-print trailing whitespace for blank lines inside block commentsBrian Anderson-2/+10
2011-08-18Try harder to disambig blocks followed by various exprs in pprust. Closes #840Brian Anderson-15/+74
As it turns out, it's not just unops we need to worry about. Also tuples and anything that requires parens.
2011-08-18Kill another case of a spurious blank line. Closes #809.Graydon Hoare-1/+1
2011-08-18Change ast::ty_ivec, ty::ty_ivec to ty_vecBrian Anderson-1/+1
2011-08-18Remove ast::ty_vecBrian Anderson-1/+0
2011-08-18Remove seq_kind from ast::expr_vecBrian Anderson-2/+2
2011-08-18Pretty-print ivecs as []Brian Anderson-5/+1
2011-08-18Remove or _-prefix all unused function argumentsMarijn Haverbeke-1/+1
This should make the compilation process a bit less noisy.
2011-08-17Allow multiple imports in a single statementBrian Anderson-0/+13
Like so: import foo::{bar, baz}; Issue #817
2011-08-17Allow multiple exports in a single export statement. Issue #817Brian Anderson-1/+5
2011-08-16Port the compiler to the expr foo::<T> syntax.Erick Tryzelaar-13/+13
2011-08-16Port the compiler to foo<T> decl syntax.Erick Tryzelaar-5/+5
2011-08-16Port the compiler to the typaram foo<T> syntax.Erick Tryzelaar-14/+14
2011-08-16Change expr foo[T] syntax to foo::<T>.Erick Tryzelaar-6/+9
This preserves the old syntax for now.
2011-08-16Change declaration type parameter syntax to foo<T>.Erick Tryzelaar-2/+2
2011-08-16Change type parameter syntax to foo<T>.Erick Tryzelaar-7/+7
This preserves the old syntax for now.
2011-08-16Removing tasks, ports and chans from the compiler.Eric Holk-34/+0
2011-08-16Rename std::ivec to std::vecBrian Anderson-19/+19
2011-08-15The wonky for...in... whitespace was bothering me. Sorry!Lindsey Kuper-24/+24
2011-08-15Pretty print lambda-blocks.Michael Sullivan-10/+41
2011-08-15Add operator 'copy', translates as fall-through.Graydon Hoare-0/+4
2011-08-15Rename a field (so that macros can mention it).Paul Stansifer-1/+1
2011-08-15rustc: Parse and typecheck unique pointersPatrick Walton-0/+4
2011-08-15Fix bad argument type of pprust::print_typeMarijn Haverbeke-27/+25
AST types are boxed, there's no need for every caller to do the unboxing
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-27 07:30:36 +0000