Update Rust

[steveklabnik]

Two things:

1. let's DRY this slightly so that we can change one version and update everything. Easier and more accurate.
2. Update to Rust 1.8.

[steveklabnik]

The rust tests are all passing, it's only other things that are failling.

[jadbox]

@steveklabnik Can you update this to Rust 1.9 (was released this week with several perf improvements, notably strings).

[steveklabnik]

I can and will! It'll be tomorrow though.

[steveklabnik]

I pushed a new commit that updates to 1.9, and upgrades some other versions. Let's see what CI says!

[steveklabnik]

All rust stuff passed, this should be good to go!

[NateBrady23]

Hi @steveklabnik we are getting ready to start our preview runs for round-13. In the meantime we are preparing to start work on verifying pull requests for round-14. Because of this, we are slightly restructuring our branches. Would you mind closing this and making a pull request that targets the new round-14 branch? Thanks!

Here's more information: http://frameworkbenchmarks.readthedocs.io/en/latest/Development/Contributing-Guide/#github-pull-request-procedure

[steveklabnik]

Absolutely!

So you know what the schedule is? It'd be nice if we could maybe work on doing some work before the next benchmark is taken.

On Jun 15, 2016, 00:17 +0100, Natenotifications@github.com, wrote:

Hi@steveklabnik(https://github.com/steveklabnik)we are getting ready to start our preview runs for round-13. In the meantime we are preparing to start work on verifying pull requests for round-14. Because of this, we are slightly restructuring our branches. Would you mind closing this and making a pull request that targets the new round-14 branch? Thanks!

Here's more information:http://frameworkbenchmarks.readthedocs.io/en/latest/Development/Contributing-Guide/#github-pull-request-procedure

—
You are receiving this because you were mentioned.
Reply to this email directly,view it on GitHub(#2031 (comment)), ormute the thread(https://github.com/notifications/unsubscribe/AABsihTcju37Eqh4yS6fNiuc-jEYPnQKks5qLzZzgaJpZM4IQcBB).

[NateBrady23]

@steveklabnik we won't be getting any work in for round-13 but with this new model we'll be able to do simultaneous testing and merging of current and future rounds so when, like now, a round is "frozen" we won't have PRs sitting waiting for feedback. We can get them tested and merged in to the round they're targeting. This also gets us closer to a continuous benchmarking goal. We want the contributors to see faster turnaround on all the hard work they do!

[steveklabnik]

Cool. 👍 sending new PR now