Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Oct 4, 2012
  1. @brson
Commits on Sep 12, 2012
  1. @brson
Commits on Aug 6, 2012
  1. @brson
  2. @brson

    Switch alts to use arrows

    brson authored
Commits on Aug 2, 2012
  1. @brson

    Convert ret to return

    brson authored
Commits on Jul 10, 2012
  1. @brson

    test: Fix shootout-binarytrees

    brson authored
Commits on May 26, 2012
  1. @brson
Commits on May 24, 2012
  1. @brson

    bench: Add hard mode to benchmarks. Activate with RUST_BENCH.

    brson authored
    RUST_BENCH is on automatically when running `make perf`
Commits on Jan 15, 2012
  1. @brson

    bench: Lower the default inputs on many shootout benchmarks

    brson authored
    Make them run a bit faster during normal testing
  2. @brson
  3. @brson

    bench: Update shootout-binarytrees to use unique boxes

    brson authored
    Shared boxes have a huge performance overhead due to #1493
Commits on Sep 2, 2011
  1. @brson
Commits on Aug 31, 2011
  1. @brson
Commits on Aug 20, 2011
  1. @brson


    brson authored
    This changes the indexing syntax from .() to [], the vector syntax from ~[] to
    [] and the extension syntax from #fmt() to #fmt[]
Commits on Aug 3, 2011
  1. @brson
Commits on Aug 2, 2011
  1. @brson
Commits on Jul 24, 2011
  1. @brson

    The Big Test Suite Overhaul

    brson authored
    This replaces the make-based test runner with a set of Rust-based test
    runners. I believe that all existing functionality has been
    preserved. The primary objective is to dogfood the Rust test
    A few main things happen here:
    1) The run-pass/lib-* tests are all moved into src/test/stdtest. This
    is a standalone test crate intended for all standard library tests. It
    compiles to build/test/stdtest.stageN.
    2) rustc now compiles into yet another build artifact, this one a test
    runner that runs any tests contained directly in the rustc crate. This
    allows much more fine-grained unit testing of the compiler. It
    compiles to build/test/rustctest.stageN.
    3) There is a new custom test runner crate at src/test/compiletest
    that reproduces all the functionality for running the compile-fail,
    run-fail, run-pass and bench tests while integrating with Rust's test
    framework. It compiles to build/test/compiletest.stageN.
    4) The build rules have been completely changed to use the new test
    runners, while also being less redundant, following the example of the
    recent rewrite.
    It adds two new features to the cfail/rfail/rpass/bench tests:
    1) Tests can specify multiple 'error-pattern' directives which must be
    satisfied in order.
    2) Tests can specify a 'compile-flags' directive which will make the
    test runner provide additional command line arguments to rustc.
    There are some downsides, the primary being that Rust has to be
    functioning pretty well just to run _any_ tests, which I imagine will
    be the source of some frustration when the entire test suite
    breaks. Will also cause some headaches during porting.
    Not having individual make rules, each rpass, etc test no longer
    remembers between runs whether it completed successfully. As a result,
    it's not possible to incrementally fix multiple tests by just running
    'make check', fixing a test, and repeating without re-running all the
    tests contained in the test runner. Instead you can filter just the
    tests you want to run by using the TESTNAME environment variable.
    This also dispenses with the ability to run stage0 tests, but they
    tended to be broken more often than not anyway.
Something went wrong with that request. Please try again.