This Week In Rust: This Week in Rust 114 |
Hello and welcome to another issue of This Week in Rust! Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. This is a weekly summary of its progress and community. Want something mentioned? Tweet us at @ThisWeekInRust or send us an email! Want to get involved? We love contributions.
This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR.
This week's edition was edited by: nasa42, brson, and llogiq.
164 pull requests were merged in the last week.
See the triage digest and subteam reports for more details.
str::replace
take a pattern.impl
for Box
from String.Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:
Every week the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now. This week's FCPs are:
[
to the FOLLOW(ty) in macro future-proofing rules.for
loop desugaring to use language items.IndexAssign
trait that allows overloading "indexed assignment" expressions like a[b] = c
.alias
attribute to #[link]
and -l
.some!
macro for unwrapping Option more safely.volatile_load
and volatile_store
intrinsics as ptr::volatile_read
and ptr::volatile_write
.If you are running a Rust event please add it to the calendar to get it mentioned here. Email Erick Tryzelaar or Brian Anderson for access.
Tweet us at @ThisWeekInRust to get your job offers listed here!
This week's Crate of the Week is toml, a crate for all our configuration needs, simple yet effective.
Thanks to Steven Allen for the suggestion.
Submit your suggestions for next week!
Borrow/lifetime errors are usually Rust compiler bugs. Typically, I will spend 20 minutes detailing the precise conditions of the bug, using language that understates my immense knowledge, while demonstrating sympathetic understanding of the pressures placed on a Rust compiler developer, who is also probably studying for several exams at the moment. The developer reading my bug report may not understand this stuff as well as I do, so I will carefully trace the lifetimes of each variable, where memory is allocated on the stack vs the heap, which struct or function owns a value at any point in time, where borrows begin and where they... oh yeah, actually that variable really doesn't live long enough.
Thanks to Wa Delma for the suggestion.
Submit your quotes for next week!
http://this-week-in-rust.org/blog/2016/01/18/this-week-in-rust-114/
Комментировать | « Пред. запись — К дневнику — След. запись » | Страницы: [1] [Новые] |