matze 

@matze
52 Followers
111 Following
361 Posts

Yay, 37ยฐC, so why not celebrate it with a 3.7.0 release of the #rustlang wastebin pastebin? New minor version bump because of the new i18n feature with Chinese and German translations and the possibility for API clients to delete pastes (yes, yes, effectively to please the machine). On top there are aesthetic changes to the Markdown rendering (hanging punctuation! admonition block fixes!) which I forgot to list ๐Ÿ™ˆ

https://github.com/matze/wastebin/releases/tag/3.7.0

Release 3.7.0 ยท matze/wastebin

Added Internationalization (i18n) support and initial Chinese and German translations. Signed owner token in the JSON insert response for easier API-based deletions. Full Changelog 3.6.2...3.7.0

GitHub

@innocentzero I don't think much has changed except for async fn in traits and async closure, both which feel like lifting restrictions but haven't actually permeated the ecosystem much.

In terms of resources I always reach out to @yosh's series on (tree) structured concurrency and anything async: https://blog.yoshuawuyts.com/

Yosh Wuyts โ€” Blog

@jhpratt thanks for the quick action. I saw and subscribed to the issues right away. It just feels a bit less than coincidental when I almost never face upgrade issues and there are two occurrences in a row. Bad luck ๐Ÿ˜‘
Something's fishy. Two days in a row I hit semver incompatible #rustlang dependency updates. time-rs first, now dropbox's alloc-stdlib via brotli.
@3timeslazy TIL repos are now private by default ๐Ÿ™ˆ that used to be a paid for feature
@3timeslazy that must be GitHub for you. Microsoft improving that service bit by bit.

My take on the comman-and-question-mark topic: https://github.com/matze/shelley. Why? No huge ass bun or npm required for pi. And #rust. That's it.

P.S.: I also tried zerostack instead of pi but it was quite a hassle. I'll keep an eye on it though.

gm tanglers! its time for the release thread ๐Ÿงต โญ you can now access CI logs right from your terminal, with plain ol' SSH โญ 1. push your changes 2. if CI is triggered, the knot will give you an ssh command 3. paste that into a new shell 4. live tail CI logs! watch to know more: 1/5
I wrote about my async-first spinner and progress bar crate beginning of the year. I'd say it progressed far enough to give the ol' one-oh. Check it out at either https://github.com/matze/strides or https://tangled.org/matze.lol/strides (yeah, that's where my #tangled experience came from).
@dngrs @jbz and? That enables multi threaded executors but does not require futures to be Send and Sync. It's when you tokio::task::spawn a future that all of a sudden the future must implement those.