Тёмный
No video :(

Rust Release Train 1.75 

chris biscardi
Подписаться 30 тыс.
Просмотров 11 тыс.
50% 1

Rust 1.75 includes Async functions in Traits!
Rust operates on a 6 week release cycle. Every 6 weeks a "release train" leaves the station and begins its journey to being the next stable release.
Code: github.com/rus...
Rust Release Post: blog.rust-lang...
RPITIT Post: blog.rust-lang...
What is a Release Train? -- doc.rust-lang....
Chapters
00:00 Rust 1.75!
00:15 code layout optimizations for rustc
00:41 Option::as_slice
02:14 exhaustive half-open usize/isize ranges
03:17 FileTimes
04:35 Return Position Impl Trait in Trait (RPITIT)
06:19 async functions in traits!
08:29 Downsides to RPITIT
09:24 new trait_variant crate

Опубликовано:

 

14 авг 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 17   
@samuelgunter
@samuelgunter 7 месяцев назад
for those who are wondering what "release train" means and are too afraid to ask (or never questioned it), "The release train is a technique for coordinating releases across multiple teams or components that have runtime dependencies. All releases happen on a fixed and reliable schedule regardless of whether all expected features are ready (the train doesn't wait for you - if you miss it you wait for the next one)" -- ThoughtWorks
@chrisbiscardi
@chrisbiscardi 7 месяцев назад
Rust specifically operates on a 6 week release cycle. A nightly release goes out every day, and a beta release is branched every 6 weeks. If the beta release doesn't have any major regressions, it is promoted to stable six weeks later. For example, the release that will go out on Feb 8th has already been branched off on December 22nd. doc.rust-lang.org/book/appendix-07-nightly-rust.html#choo-choo-release-channels-and-riding-the-trains
@friendlywavingrobot
@friendlywavingrobot 7 месяцев назад
chris is the hardest working rust reporter out there. Great vid!
@mikkelens
@mikkelens 7 месяцев назад
The bit at the end of the blog post detailing future stabilization of the parallelized compiler front end makes me quite excited. I am happy to finally see RPITIT/AFIT a reality for crates, just not sure how this will look ergonomically in "public" contexts (between crates, which is warned against as of now) in the future.
@houstonbova3136
@houstonbova3136 7 месяцев назад
This feels like a lot of really nice quality of life improvements.
@kira.herself
@kira.herself 7 месяцев назад
rust gets better by each day yippee
@lixou
@lixou 7 месяцев назад
Waiting for the summary Video all day long 🎉
@jacekm.1789
@jacekm.1789 7 месяцев назад
thanks for the update! as always useful!
@ravveni
@ravveni 7 месяцев назад
awesome summary! thanks!
@Roms8313
@Roms8313 7 месяцев назад
this is HUGE 😮❤
@ducky_futures
@ducky_futures 7 месяцев назад
Can you pretty please teach us how to make custom rounds? Like those you see on prop hunt with no loading screen between rounds. Here is what I found on the UEFN dev site. Thank you! “I “Fake” rounds in multiple of my maps for the very reason of how bad the round change over time is. (You will literally loose players as they wait for the black screen to change over) As long as you are clear on when the round will end (Time based / Objective based / etc) then I feel you can do better then the round system in place. When I have things that need to get reset this is how I handle it: My GameManager (Verse device) will include a ResetTrigger editable variable that I Trigger in verse when I’m ready to do clean up. Then my devices I either want to disable or enable, item removers that need to take player items, portals that need to relocate players, all listen to the ResetTrigger. This simplifies the control flow of the state of your game loop. You will of course have to handle resetting other things in an appropriate way as well. For example some of my verse devices will listen to a reset trigger (or have a Reset function that gets called by some other device directly) then the device will do something like clear an array or change a variable the is referenced to a player in a map, etc.”
@zed5790
@zed5790 7 месяцев назад
Please make a video on rust Loco Framework.
@Saturate0806
@Saturate0806 7 месяцев назад
why did you call await on fetch in main if the last function call inside async fetch was an await?
@chrisbiscardi
@chrisbiscardi 7 месяцев назад
The trait function is defined as async, which desugars to a function that returns `impl Future` regardless of if the last value in the function body is a "regular" value or not. The full return type in this case is impl Future So you await on that Future in main when you call fetch().
@BrazenNL
@BrazenNL 7 месяцев назад
Early 360p crowd, represent …
@chrisbiscardi
@chrisbiscardi 7 месяцев назад
oof, haha. Hopefully its not too bad. Dashboard says 40 min left for the hd encode and 60 min left for the 4k encode.
@BrazenNL
@BrazenNL 7 месяцев назад
@@chrisbiscardiAll in HD now. Thanks!
Далее
I spent six months rewriting everything in Rust
15:11
Просмотров 420 тыс.
How to set up Rust for Advent of Code
14:18
Просмотров 37 тыс.
Sevinch Ismoilova - Xayollarim 18-Avgust 19:00 Premera
00:19
Rust vs Go: Which is best? THE Definitive Answer
28:30
The Best Games from Bevy Jam 5
9:54
Просмотров 2,5 тыс.
Iced vs Slint  | Rust GUI Wars #1
10:07
Просмотров 4,8 тыс.
Rust Release Train 1.74
14:54
Просмотров 14 тыс.
When the details matter - Niko Matsakis - EuroRust 2023
30:57
Tonic makes gRPC in Rust stupidly simple
19:08
Просмотров 46 тыс.
Why Rust is bad, actually*
11:53
Просмотров 43 тыс.
Rust Functions and Modules 🦀
21:55
Просмотров 8 тыс.
Constructors Are Broken
18:16
Просмотров 105 тыс.
Rust 1.76.0: 73 highlights in 24 minutes
23:41
Просмотров 11 тыс.