Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Jan 24, 2012
  1. @brson

    core: Format comm docs correctly

    brson committed
  2. @brson
  3. @brson
  4. @brson
  5. @kevina @brson

    Add regression test for issue #1362.

    kevina committed with brson
    Although its not really needed.  Without that fix, reported spans will
    likely be bogus if the error is within the first couple of lines
    (probable around 5) of that file.  Thus, many of the compile-fail
    tests will fail due to incorrect location.
  6. @kevina @brson
  7. @kevina @brson

    When replacing a pattern variable in macro expansion use the span of

    kevina committed with brson
    the replacement and not the span of the pattern variable.
    Fixes issue #1448, and #1387.
  8. @kevina @brson

    Allow ast_fold_precursor to change the span.

    kevina committed with brson
    This involved changing the prototype for the callbacks to thread the
    span though.  A wrapper function, fold::wrap, can be used to wrap the
    old style callbacks.
  9. @kevina @brson

    Don't reset the chpos/byte_pos to 0 in new_parser_from_source_str.

    kevina committed with brson
    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/ 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).
  10. @kevina @brson
  11. @kevina @brson

    Revert "rustc: Exclude stdin from codemap files when lookup_pos".

    kevina committed with brson
    Need a better fix, right now it is just causing even more confusion,
    for example in issue #1448 and #1387.
    This reverts commit 1e4de33.
  12. @brson
  13. @brson

    core: More doc tweaks

    brson committed
  14. @brson
  15. @brson


    brson committed
  16. @brson

    core: Add crate docs

    brson committed
  17. @catamorphism
  18. @brson

    Change rustc and rustdoc's #[desc] attribute to #[comment]

    brson committed
    There are two attributes in use for this same purpose.
  19. @brson

    Revert "rustdoc: Get the crate brief description from the 'desc' attr"

    brson committed
    This reverts commit 521e58a.
    Some crates use 'desc', some 'comment' - I want them to just use 'doc'
  20. @brson
  21. @brson
  22. @brson
  23. @brson
  24. @nikomatsakis
Commits on Jan 23, 2012
  1. @catamorphism

    Check that the names mentioned in tag exports are actually types (or …

    catamorphism committed
    Check that in export foo{}, foo is an enum type, and that in export
    foo{bar, quux}, foo is an enum type and bar and quux are variants belonging
    to foo.
  2. @catamorphism

    Export all enum variants by default; new syntax for selectively expor…

    catamorphism committed
    …ting 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.
  3. @brson
  4. @brson
  5. @brson
  6. @brson
  7. @brson

    Merge pull request #1621 from thoughtpolice/install-dot-txt

    brson committed
    Add an INSTALL.txt
  8. @brson

    Remove mention of Windows installer from tutorial

    brson committed
    We don't want users to hurt themselves, since the installer has
    a bug in 0.1 that could possibly corrupt %PATH%
  9. @thoughtpolice
  10. @brson

    Merge pull request #1620 from thoughtpolice/email-fix

    brson committed
    Fix my email in AUTHORS.txt
  11. @brson
Something went wrong with that request. Please try again.