-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
October 2022 #99
Comments
I think I could give a tour through Iterators. I'll see in the next days how much time I find to prepare something. |
I'm a little late on this. Shall we opt for a very late announcement or shall we defer the date? |
I've also been a bit AWOL for work reasons. I think delaying might be preferable to doing things super short notice. I can ask for an alternative date at the C4 on Tuesday. That would probably be the 12th or 26th, if you have a preference between those. |
Both are fine for me. I'd go for the 12th if we have a choice. |
Any news on the date? |
Yes, October 12th it is. We'll be sharing the space (not the room though) with the "Free Software Evening". |
Great, thanks. |
Uff… I feel really bad about having delayed this even further. My mail server somehow forgot how to IPv4, which led to a certain lack of GitHub notifications. And I noticed way to late. The announcement looks fine to me, and good call on putting it out there. |
ToDo
Invitation draft
Rust News
IntoFuture
has been stabilized. The.await
keyword can now be used on anything implementing itcore
/alloc
mem::uninitialized()
is now akin tomemset(buf, 0x01)
avoiding many cases of UBrust-analyzer
is now available viarustup
let else
has been stabilized, coming to Rust 1.65 (?)The text was updated successfully, but these errors were encountered: