ChanServ changed the topic of #rust-embedded to: Welcome to the Rust Embedded IRC channel! Bridged to #rust-embedded:matrix.org and logged at https://libera.irclog.whitequark.org/rust-embedded, code of conduct at https://www.rust-lang.org/conduct.html
Noah[m] has joined #rust-embedded
<Noah[m]> Is anyone at c3 (Chaos Communication Congress) this year? :)
cr1901_ is now known as cr1901
emerent has quit [Ping timeout: 248 seconds]
emerent has joined #rust-embedded
rom4ik has quit [Quit: bye]
rom4ik has joined #rust-embedded
Foxyloxy has quit [Quit: Textual IRC Client: www.textualapp.com]
Foxyloxy has joined #rust-embedded
igiona[m] has quit [Quit: Idle timeout reached: 172800s]
RockBoynton[m] has joined #rust-embedded
<RockBoynton[m]> is there a technical reason why defmt doesn't support having the identifier within the brackets instead of as a vararg, e.g. println!("hello, {world}")?
esden[cis] has quit [Quit: Idle timeout reached: 172800s]
<thejpster[m]> I think the problem is that - given the string "hello, {world}" and and a byte buffer containing 04 00 01 00 00 00, how are you going to render that?
<thejpster[m]> You could I guess make the macro re-write the format string to use numbered arguments and emit the rewritten string. But basically rendering the string involves walking it, finding each arg, and then popping the appropriate number of bytes off the byte buffer.
<thejpster[m]> (the byte buffer is 0x0004 which might be a string ID for the string {=u32}, assuming world: u32 and 0x00000001 which is a value for world as a 32-bit integer)
<thejpster[m]> the rule is - if the format string arg has a specified type, you can pull the raw value straight from the stream, and if it doesn't, pull an interned format string ID and then do whatever that says do.
<scorpion2185[m]1> i am now adding a timer in https://github.com/jonlamb-gh/pinetime-rs/
<scorpion2185[m]1> >Rust & RTIC running on the PineTime watch.
<scorpion2185[m]1> how can I make some "ticker" to update each x secs without losing the time that is used to draw etc.?
<scorpion2185[m]1> * i am now adding a timer in https://github.com/jonlamb-gh/pinetime-rs/
<scorpion2185[m]1> how can I make some "ticker" to update each x secs without losing the time that is used to draw etc.?
<scorpion2185[m]1> >Rust & RTIC running on the PineTime watch.
i509vcb[m] has quit [Quit: Idle timeout reached: 172800s]
<scorpion2185[m]1> i saw fugit but idk https://docs.rs/fugit/latest/fugit/struct.Duration.html#method.from_ticks
therealprof[m] has quit [Quit: Idle timeout reached: 172800s]
adamgreig[m] has quit [Quit: Idle timeout reached: 172800s]
bartmassey[m] has quit [Quit: Idle timeout reached: 172800s]
<Noah[m]> rahix: can we enter probe-rs on the assembly list here: https://events.ccc.de/congress/2024/hub/en/assembly/rust-lang/? :)
rahix[m] has joined #rust-embedded
<rahix[m]> Noah: for sure! :)
<Noah[m]> rahix[m]: can i edit it smh?
loki_val has quit []
crabbedhaloablut has joined #rust-embedded
vollbrecht[m] has joined #rust-embedded
<vollbrecht[m]> scorpion2185[m]1: in general the idea behind this trait crates is that your HAL or yourself would provide a implementation, so user code can be simpler be shared. But every architecture would need its own implementation.
<vollbrecht[m]> * would need to provide its own
<vollbrecht[m]> * a implementation in some library form, so, * would need to provide its own
petekubiak[m] has quit [Quit: Idle timeout reached: 172800s]