For our November meeting, Jim Blandy will be presenting his OSCON Amsterdam talk Concurrency in Rust! By comparing a seemingly simple problem's implementation in an older language to Rust's performance, Jim makes his subject matter accessible to new Rust users while remaining useful to experts.

Join us in #pdxrust on irc.freenode.net (http://webchat.freenode.net/)!

Remember that Rust's Code of Conduct applies to this event.

Tokio, backed by the Rust futures library, has a unique execution model. The talk will do a deep dive, explaining the context, rational, and how it is implemented

Tokio author Carl Lerche will  explain how the tokio-core reactor is implemented. Attendees will have an easier time following along if they've read Rust's beginner documentation, but no prior knowledge of Tokio or futures is required.

PDXRust does not provide food, though you're welcome to bring food with you or head to dinner with other Rustaceans afterwards. 

We follow the Rust Code of Conduct.

Come hack on Rust projects with us! Write your first Rust crate, contribute to an open source Rust project, team up with someone else on a cool new Rust tool, or even hack on rustc itself!

Lucky Lab has food and drinks and lots of open seating.

We follow the Rust Code of Conduct.

See you there!

PSU Computer Science professor Bart Massey has mentored a variety of capstone projects using Rust, as well as writing a variety of projects in the language. He'll tell us about some chess playing code that he wrote in Rust.

Food is not provided at the meetup, thoguh carts are nearby if you'd like to grab a bite before and many Rustaceans are in the habit of going to dinner together afterwards. Expectations for the meetup are set forth in the Rust Code of Conduct; contact any of the organizers if you have a concern.

Sorry for the late notice on this one -- Nick will be hosting a hack night with optional lightning talks for our September meeting.

Bart is back, this time to tell us stories and answer questions about 25 bite-sized pieces of Rust! 

Check out the code at https://github.com/BartMassey/advent-of-code-2016 if you'd like to put him on the spot with questions.

Bart also organizes some Portland State University Capstone projects, so if you're pondering where to find a team of eager Rustaceans who'll write open source code for university credit, he's the person to talk to.

As always, remember that you can request future meetup topics or volunteer to speak in the issue tracker: https://github.com/pdxrust/meetups/issues

Matthew will be sharing his journey with Rusoto, Rust's unofficial AWS SDK. He'll cover how Rusoto came about, what it's like working on it, and how it works as well as examples of how it can be used.

This month, Shea Newton will be presenting "Writing Software That's Safe Enough To Drive A Car!"

Autonomous cars run on software, and most of the microcontrollers in today's cars are programmed using C. We have found that even the best code checking for C does not protect against system-crippling errors - the kind of errors that could endanger the lives of future drivers. C is simply not the right language for safety-critical software, but what about Rust?

## Target audience

I'd like to try and keep this talk relatively high level. Examples of self-corrupting code may resonate more with developers who have written C but ideally the talk will apply to anyone interested in Rust and curious about the state of self-driving car technology.

------------------------------------------------------------------

We may also have time for lightning talks and socializing as well.

------------------------------------------------------------------

As always, we'll be following the Rust Code of Conduct: https://www.rust-lang.org/en-US/conduct.html