summary refs log tree commit diff
path: root/src/libsyntax
AgeCommit message (Collapse)AuthorLines
2013-02-25libsyntax: fix the span in parse_bottom_expr's INTERPOLATED handlerErick Tryzelaar-12/+17
2013-02-25Stop parsing capture clausesBen Striegel-38/+20
2013-02-25libsyntax: make lexer vecs_implicitly_copyable-freeErick Tryzelaar-8/+17
2013-02-25libsyntax: progress on making syntax::visit vecs_implicitly_copyable-freeErick Tryzelaar-718/+833
2013-02-25libsyntax: convert visit to pass ty_params by referenceErick Tryzelaar-252/+315
2013-02-25libsyntax: minor cleanupErick Tryzelaar-23/+24
2013-02-25libsyntax: add explicit modes where required to copy strs/vecsErick Tryzelaar-76/+106
2013-02-25libsyntax: Convert ast::attribute_ to store a @meta_itemErick Tryzelaar-17/+18
2013-02-22libsyntax: Remove all mutable fields from libsyntax. rs=demutingPatrick Walton-5/+5
2013-02-22libsyntax: De-mut the parser. rs=demutingPatrick Walton-333/+332
2013-02-22libsyntax: De-mut the macro parser. rs=demutingPatrick Walton-12/+12
2013-02-22libsyntax: De-mut the pipe compilerPatrick Walton-37/+39
2013-02-22auto merge of #5081 : brson/rust/pipes, r=pcwaltonbors-21/+23
r?
2013-02-21auto merge of #5077 : jbclements/rust/increase-monomorphization-depth-limit, ↵bors-21/+75
r=catamorphism It appears that using deriving_eq/auto_encode on ASTs bumps up against the "gee this looks like infinite unfolding" limit of 10 in monomorphization. Increasing it to 30 seems to solve this problem for me.... Also, commenting and a few renames.
2013-02-21auto merge of #5076 : pcwalton/rust/demuting, r=pcwaltonbors-14/+14
2013-02-21core: Extract comm from pipes. #4742Brian Anderson-21/+23
2013-02-21auto merge of #5075 : luqmana/rust/derec, r=catamorphismbors-1/+1
Now only `lib core/pipes.rs` has `#[allow(structural_records)]`. That can be removed after a snapshot.
2013-02-21auto merge of #5059 : Kimundi/rust/incoming, r=catamorphismbors-3/+3
compiles-as-is, but needs a snapshot to remove the `stage0`ed extfmt export in core. Closes #4750
2013-02-21Cleanup, commenting, trivial renamingJohn Clements-21/+75
2013-02-21librustc: De-mut some of transPatrick Walton-14/+14
2013-02-21Remove the last bits of structural records from tests/rustc/rusti/rustpkg.Luqman Aden-1/+1
2013-02-21auto merge of #5068 : sethpink/rust/derive-eq-tuple-struct, r=catamorphismbors-14/+89
Previously an unimplemented error was thrown when using #[deriving_eq] on tuple-like struct definitions.
2013-02-21auto merge of #5071 : luqmana/rust/derec, r=pcwaltonbors-224/+315
Rid libsyntax of records and get rid of the last piece in `librustc/front/test.rs`.
2013-02-21librustc: Separate the rest of the trait bounds with `+` and stop parsing ↵Patrick Walton-3/+14
space-separated ones. rs=plussing
2013-02-21Moved core::extfmt to core::private::extfmtMarvin Löbel-3/+3
Needs a snapshot to remove stage0 extfmt export in core
2013-02-21Get rid of structural records in libsyntax and the last bit in librustc.Luqman Aden-224/+315
2013-02-21Implement #[deriving_eq] on tuple like structsSeth Pink-14/+89
2013-02-20librustc: Separate most trait bounds with '+'. rs=plussingPatrick Walton-21/+21
2013-02-20librustc: Get rid of structural records save for front/test.rs.Luqman Aden-2/+2
2013-02-19auto merge of #4999 : erickt/rust/incoming, r=brsonbors-333/+369
This patch series is doing a couple things with the ultimate goal of removing `#[allow(vecs_implicitly_copyable)]`, although I'm not quite there yet. The main change is passing around `@~str`s in most places, and using `ref`s in others. As far as I could tell, there are no performance changes with these patches, and all the tests pass on my mac.
2013-02-19convert SyntaxExtensions's key to a @~strErick Tryzelaar-31/+31
2013-02-19convert ast::meta_items to take @~strsErick Tryzelaar-33/+34
2013-02-19convert syntax::attr to use @~strsErick Tryzelaar-88/+84
2013-02-19Alias HashMap<~str, SyntaxExtension> to SyntaxExtensionsErick Tryzelaar-6/+8
2013-02-19libsyntax and librustc: minor cleanupErick Tryzelaar-7/+5
2013-02-19libsyntax: change attr:get_attr_name to take a refErick Tryzelaar-9/+8
2013-02-19libsyntax: make enum variants take refsErick Tryzelaar-104/+150
2013-02-19syntax: fix the indentation of a functionErick Tryzelaar-36/+36
2013-02-19Change functions from taking ~str to taking &strErick Tryzelaar-3/+3
2013-02-19libsyntax: convert interner into a modern structErick Tryzelaar-42/+36
2013-02-19auto merge of #5002 : catamorphism/rust/one-tuples, r=graydonbors-8/+37
r? @graydon - This is for greater uniformity (for example, macros that generate tuples). rustc already supported 1-tuple patterns, but there was no way to construct a 1-tuple term. @graydon , as far as your comment on #4898 - it did turn out to be solvable inside the macro (since @luqmana already fixed it using structs instead), but I still think it's a good idea to allow 1-tuples, for uniformity. I don't think anyone is likely to trip over it, and I'm not too worried that it changes the amount of ambiguity.
2013-02-18auto merge of #5005 : alexcrichton/rust/bitv++, r=catamorphismbors-4/+8
These commits take the old bitv implementation and modernize it with an explicit self, some minor touchups, and using what I think is some more recent patterns (like `::new` instead of `Type()`). Additionally, this adds an implementation of `container::Set` on top of a bit vector to have as a set of `uint`s. I initially tried to parameterize the type for the set to be `T: NumCast` but I was hitting build problems in stage0 which I think means that it's not in a snapshot yet, so it's just hardcoded as a set of `uint`s now. In the future perhaps it could be parameterized. I'm not sure if it would really add anything, though, so maybe it's nicer to be hardcoded anyway. I also added some extra methods to do normal bit vector operations on the set in-place, but these aren't a part of the `Set` trait right now. I haven't benchmarked any of these operations just yet, but I imagine that there's quite a lot of room for optimization here and there.
2013-02-18auto merge of #5004 : luqmana/rust/rename-use-import, r=catamorphismbors-14/+14
Seems like my previous pull request got lost along the way somehow. So here it is updated.
2013-02-18rustc: For one-tuples, make parsing and printing the type workTim Chevalier-2/+14
and add a test to reflect-visit-data
2013-02-17Modernize bitv mut fields and explicit selfAlex Crichton-4/+8
2013-02-17libsyntax: Update view_item_use/import to reflect actual usageLuqman Aden-14/+14
2013-02-17syntax: Allow 1-tuple expressionsTim Chevalier-6/+23
This is for greater uniformity (for example, macros that generate tuples). rustc already supported 1-tuple patterns, but there was no way to construct a 1-tuple term.
2013-02-17libsyntax: Long lines.Luqman Aden-6/+12
2013-02-17libsyntax: Explicit-self-ify pipes compiler.Luqman Aden-122/+110
2013-02-17libsyntax: Remove last use of structural records in pipes compiler.Luqman Aden-56/+69
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-04 09:11:02 +0000