06:15 <thejpster[m]> <whitequark[cis]> "the approach i've taken in..." <- I have slides on this

06:15 <thejpster[m]> https://rust-training.ferrous-systems.com/latest/slides/generics#/14

06:16 <thejpster[m]> I say the same about &’a str vs String.

07:04 <MartinSivk[m]> <dngrs[m]> "I like to write type aliases..." <- Oh, I have this too of course. It almost looks like type programming with multiple levels of aliases `I2cProxy<Forward<I2c<I2C1, BoardI2cSda, BoardI2cScl>, ()>>`. But I was porting my project to a different board and had to do a second (and third and then v1 + compat traits...) copy of all those manually instead of the inference engine doing it for me. Which should be possible in

07:04 <MartinSivk[m]> theory as all the types are clear after the first assignment, but of course implementing that level of inference in the compiler is hard.

08:35 <be[m]> <RobinMueller[m]> "Does anyone have experience with..." <- bisync is great. You can deal with embedded_hal vs embedded_hal_async traits by importing the symbols into the module, then inside the implementation modules, use relative paths like `... (full message at

08:35 <be[m]> <https://catircservices.org/_irc/v1/media/download/AZdLu6ZqcKWF5tbcDNetXm3j_mq1gy0FG42Shpuy0-i8LB0suyQBMu64jCgBqctaas4_jaMoWjhxOeeS7GzTANC_8AAAAAAAAGNhdGlyY3NlcnZpY2VzLm9yZy9YRGJFcmJZdEhDV2xKWVVKbGxvcUtGaXQ>)

08:36 <be[m]> then in one of the implementation submodules, I have use super::super::{bisync, DelayNs, SpiDevice};

08:40 <be[m]> <SEGFAULT[m]> "I need to get one of those..." <- When I realized I needed one of those to not have to physically press a button on the device every time I wanted to flash a Raspberry Pi Pico, instead of buying one of those programmers, I just bought an ESP32-C3 devboard that exposes JTAG over USB and defmt just works.

08:41 <be[m]> * those programmers, for about the same cost I just

08:43 <be[m]> * When I realized I needed one of those to not have to physically press a button on the device every time I wanted to flash a Raspberry Pi Pico, instead of buying one of those programmers, for about the same cost I just bought an ESP32-C3 devboard that exposes JTAG over USB and defmt & probe-rs just work.

14:10 <thejpster[m]> ping again on https://github.com/rust-embedded/cortex-ar/pull/23 please

14:50 <burrbull[m]> <MartinSivk[m]> "Folks, I think I have seen a..." <- In f4xx-hal I use enums of possible alternate pins associated with peripheral. So I can keep pins inside peripheral instance without PINS generic.

14:51 <burrbull[m]> * alternate pins (generated from Cube db) associated with, * PINS generic. https://github.com/stm32-rs/stm32f4xx-hal/blob/master/src/gpio/alt.rs

15:01 <rafael[m]> <wassasin> "Sounds like something else is..." <- remember this one? I am fairly certain you are right something else is going on, but after more testing i have written this off as an oddity of the dfplayer. Just for entertainment value: There is a stupidly simple solution to the track count... so easy that i did not see it even when it was right in front of me. You can just send the player a command to play a unreasonably high track

15:01 <rafael[m]> number (volume set to 0), after which it will proceed to play the highest available track. You can then send a query command to retrieve the currently playing track no. Done, got a track count. Feels as hacky as it is, but is even just as fast than the actual counting is. 😄

15:04 <MartinSivk[m]1> burrbull: Yeah, that looks like the pattern I was looking for. It looks like the Into<> part is what I need to figure out. I had the type definition traits.

15:22 <MartinSivk[m]1> burrbull: The pin! macro is quite a piece of work, it will take me a while to decipher

20:08 <mux3dup[m]> Hello, new here!... (full message at <https://catircservices.org/_irc/v1/media/download/AXyoN2HFdev12Ta7pRil3Lsdd7-JVU3L0KehQXss-CQf-K97ZmHWD5eY27_k4Ca-15S4fpBK12gLFKV3EHTQol2_8AAAAAAAAGNhdGlyY3NlcnZpY2VzLm9yZy9UZUpYSXZFUnVJZlhVVGt2dVNrSVhyaXM>)