Provide workaround for lifetime bug in rustlang

[worr]

Due to rust-lang/rust#22252, r-value temporaries
outlive the lifetimes of variables bound with let statements in a function
body. Because of this, device.rs fails to compile against newer rustc
nightlies.

This implements a simple workaround that binds the result of the match in
request_code to a local variable before returning it. This allows it to have
the same lifetime as req in one of the previous let bindings.

[GitCop]

Thanks for contributing. Unfortunately I have to tell you that there were the following issues with your Pull Request

• Commit: 9649efc
  • Your commit message body contains a line that is longer than 72 characters
  • Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#-git-commit-guidelines

---

This message was auto-generated by https://gitcop.com

[GitCop]

Thanks for contributing. Unfortunately I have to tell you that there were the following issues with your Pull Request

• Commit: 12f5052
  • Your commit message body contains a line that is longer than 72 characters

Guidelines are available at https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#-git-commit-guidelines

---

This message was auto-generated by https://gitcop.com

[Byron]

Thank you !
It's odd that I didn't see this 3-months old bug yet, the compiler I am using is rustc 1.1.0-nightly (7bd71637c 2015-05-06) (built 2015-05-05).
I will merge it and make a point-release, along with a ticket to trigger a review once Rust 1.0 is out.

[Byron]

Sad, the release will have to wait as crates.io seems down :(.

[Byron]

It's interesting: This issue has recently been introduced, and occurs from rustc 1.1.0-nightly (dc630d01e 2015-05-09) (built 2015-05-09) or before that, but worked with the version I posted previously.

[Byron]

New release published: v0.4.5