This Week In Rust: This Week in Rust 398 |
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 a pull request. 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.
fcp 0.2.0 released - A significantly faster alternative to cpThis week's crate is css-inline, a crate to inline CSS into style tags.
Thanks to Dmitry Dygalo for the suggestion.
Submit your suggestions and votes for next week!
Always wanted to contribute to open-source projects but didn't know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!
Some of these tasks may also have mentors available, visit the task page for more information.
Synth
Sycamore
If you are a Rust project owner and are looking for contributors, please submit tasks here.
297 pull requests were merged in the last week
ForceWarn a lint leveltcx allocated allocationsis_multilineloopcheck_expr_return()no_global_oom_handling: disable new()s, pin()s, etc.str::from_utf8_unchecked as conststring_drain_as_strBound::cloned()Seek::rewind()process::Command on Windows, environment variable names must be case-preserving but case-insensitivetrack_path::path fn for usage in proc_macrosround and roundfoffline and frozencargo clippy --fixnonstandard_macro_braces to nurserydoc(hidden) or unstable variants in wildcard lintproc_)macros for nonstandard_macro_braces lintdoc_markdown false positiverc_mutexstrlen_on_c_stringsdisallowed_script_identsA fairly mixed week with improvements and regressions mostly balancing themselves out. The highlight of this week is we have now started to adopt a new performance triage process which will label PRs that introduce performance regressions with the perf-regression label. Authors and/or reviewers are expected to justify their performance regression either by a short summary of why the change is worth it despite the regression or by creating an issue to follow-up on the regression.
We hope this process will lead to better compiler performance in the long term.
Triage done by @rylev. Revision range: 5a78340..9a27044
2 Regressions, 3 Improvements, 2 Mixed 1 of them in rollups
Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:
No RFCs were approved 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.
#[derive(Default)] on enums with a #[default] attributeimpl From<[(K, V); N]> for HashMap (and friends)No new RFCs were proposed this week.
.*-?(lang|script)\If you are running a Rust event please add it to the calendar to get it mentioned here. Please remember to add a link to the event too. Email the Rust Community Team for access.
StructionSite
ChainSafe Systems
InfinyOn
Merantix
NORICS GmbH
NZXT
Parity Technologies
Esturary
Kraken
Subspace Network
Tweet us at @ThisWeekInRust to get your job offers listed here!
One thing I like about Rust is that it filters out lazy/sloppy thinkers. Even when I disagree with another Rust programmer, there is a certain level of respect that comes from knowing that they thought about the problem deeply enough to pass the borrow checker.
Thanks to Jonah for the self-suggestion!
Please submit quotes and vote for next week!
This Week in Rust is edited by: nellshamrell, llogiq, and cdmistman.
https://this-week-in-rust.org/blog/2021/07/07/this-week-in-rust-398/
| Комментировать | « Пред. запись — К дневнику — След. запись » | Страницы: [1] [Новые] |