Closed Florob closed 1 year ago
@kawogi We still need a topic to announce.
My pool of ideas is always somewhat restricted to things I'm currently working on/with and things we haven't talked about in a while. Currently "working on/with" is proc-macro derive and embedded Rust. However, I don't really feel comfortable talking about either (yet). In terms of things we haven't talked about for a while traits come to mind. Topics like general overview, use-cases, and Fn traits. Possibly two smaller talks split among us if you'd be up for that.
I'm also struggling to find a good topic. Embedded is on my list as well (but I'm not there, yet). Same with cranelift. I thought about talking about something very basic, like explaining Option to beginners. Niche optimization would be the most advanced bullet point then. Traits sound like a good topic, but it might be challenging to make it fit into the time available.
Traits sound like a good topic, but it might be challenging to make it fit into the time available.
There are recordings from last time around (overview, Fn* traits). Each talk was ~30min, so I wouldn't really worry about that.
Ok, let's opt for traits then.
Some bullet points I could imagine (increasing complexity):
ToString
is very approachable)impl
keyword to simplify method signaturesToString
as example again)Index
or Iterator
)I could cover 1..=8
and leave 9 up to your experience. Are you okay with that?
If I don't find the time to prepare a presentation I'll resort to live coding.
@Florob Oh damn, I totally forgot another personal appointment which collides with Feb 1st. Very sorry for the short notice, but can we delay the meetup to Jan 8th?
@kawogi Probably not. The other meetup that's on the 8th told me they were going to use the big room, projector, video equipment more in the future. I could still ask, but realistically that might mean I get a "No" tomorrow, leading to a very late announcement. Is it fine with you if I do the February meetup on my own?
I'm ok with being absent this time. Still better than delaying too much. Just let me know if you want to do traits anyway or move that to the next meetup.
Sorry again for the trouble :(
I just canceled tomorrow's meetup as I feel a little sick. Nothing terrible, but also not where I would attend/lead a meetup in good conscience :/.
Sorry to hear that. Get well soon!
Shall we rename that issue to March 2023 and reset the status? What shall I prepare for the next meetup? "Introduction to traits" in general (as proposed in https://github.com/Rustaceans/rust-cologne/issues/103#issuecomment-1404121470). I don't want to overlap with what you have already done.
I re-started to work on embedded Rust so I feel confident that I could host a talk about that soon (e.g. April if we feel that easter-holidays wouldn't steal us to many participants).
Shall we rename that issue to March 2023 and reset the status?
Yes, let's do that. I was pondering moving this to the 22nd, but skipping a month is probably better than back to back meetups at that point.
What shall I prepare for the next meetup? "Introduction to traits" in general (as proposed in https://github.com/Rustaceans/rust-cologne/issues/103#issuecomment-1404121470). I don't want to overlap with what you have already done.
That would still be nice. I had a basic outline done before I got sick, but I would prefer having separate talks with separate speakers.
Shall I send the meetup invitations or do you want to adjust something in the announcement? I guess this will be a new meetup rather than an update to the cancelled one, right? (I don't even know if meetup.com supports this).
I would do a new meetup on meetup.com, but probably modify the one on the website. My understanding was that you would be doing the intro talk. Did we miscommunication there? If you're going to, it would be nice to update the announcement to reflect that.
I thought
There will be a talk about traits in general, showing how to use them to make code generic and composable.
would cover that introduction part, but now I see that the next paragraph doesn't introduce a second topic. I'll suggest an update …
better?
Looks good to me.
ToDo
Invitation draft
Rust News
#[must_use]
onasync fn
std::sync::mpsc
based oncrossbeam-channel
, improved performance/correctness