00:32 <jacobrosenthal[m> I think i made something neat, not sure how to turn it into a github action though. I did a cargo-size action that triggers on merge, and stores the size in the git notes... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/vdyeDtRtDgZCGWLUDLUCNhJS>)

00:32 <jacobrosenthal[m> * I think i made something neat, not sure how to turn it into a shareable github action though. I did a cargo-size action that triggers on merge, and stores the size in the git notes... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/qRqFXnwUbBBDQujzhaRPzYyV>)

00:33 <jacobrosenthal[m> I could see versioning plugins in the notes section and having a header magic like size:v1:10 (10 lines) and you could add another note on the 11th line bloat:v2:20 (20 lines)

00:35 <jacobrosenthal[m> https://gist.github.com/jacobrosenthal/f3eed3ee224271bc57108b4611ce3929

09:30 <thejpster[m]> wut: https://github.com/rust-lang/cargo/blob/master/CHANGELOG.md#cargo-174-2023-11-16

09:30 <thejpster[m]> > Added support for target.'cfg(..)'.linker (https://github.com/rust-lang/cargo/pull/12535)

09:30 <thejpster[m]> that's neat.

09:31 <thejpster[m]> maybe we can get cargo to support the specification of a linker script - then we can get rid of rustflags entirely.

09:31 <thejpster[m]> which means people can pass RUSTFLAGS=".." on the command line without causing it to ignore the info in the cargo config.

09:52 <korken89[m]> Indeed, this is why we made a PR to specifically recommend it to flip-link

09:52 <korken89[m]> https://github.com/knurling-rs/flip-link/pull/92

09:53 <korken89[m]> It fixes a lot of ergonimic issues with -D warnings and RUSTFLAGS

09:53 <korken89[m]> * It fixes a lot of ergonomic issues with -D warnings and RUSTFLAGS

09:57 <thejpster[m]> wait, when you say "we"?

09:57 <thejpster[m]> I saw that PR (they all turn up in my inbox) and that's what started this train of though.

09:58 <thejpster[m]> s/though/thought/

10:02 <korken89[m]> thejpster[m]: We as in Mobilaris Industrial Solutions

10:02 <korken89[m]> I lead the embedded team there :)

10:03 <thejpster[m]> oh cool

10:03 <thejpster[m]> the submitter has an @volvocars.com address on their github

10:03 <korken89[m]> Yeah Nils was working in a Volvo project before joining

10:58 <braincode[m]> Is there any good BMS (Battery Management System) written in Rust nowadays (OSS)? Preferably nostd.

11:02 <braincode[m]> I'm thinking about something similar to https://foxbms.org/ w.r.t features/maturity.

11:15 <braincode[m]> s/./?/

11:26 <JamesMunns[m]> I haven't seen any

12:52 <mgudel[m]> Hey, can someone give me a hint how this "bug" is possible in _embedded-hal-mock_ (eh1 spi mock)?... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/brhdshgVYWNHmfBgblKmEefz>)

12:53 <mgudel[m]> [https://docs.rs/embedded-hal-mock/0.10.0/embedded_hal_mock/eh1/spi/type.Mock.html](https://docs.rs/embedded-hal-mock/0.10.0/embedded_hal_mock/eh1/spi/type.Mock.html)

12:53 <mgudel[m]> if you want to take a look yourself

12:53 <mgudel[m]> s/[//, s/](https://docs.rs/embedded-hal-mock/0.10.0/embedded_hal_mock/eh1/spi/type.Mock.html)//

12:55 <mgudel[m]> Nevermind, the `Error` trait is implemented...

13:08 <mgudel[m]> <mgudel[m]> "Nevermind, the `Error` trait..." <- Compiler error confused me a bit.

13:08 <mgudel[m]> Writing a good doc example that actually compiles isn't always that easy.

19:45 <thvdveld[m]> I was looking at fugit as the time crate for my project. However, the Duration is only generic over u32 or u64, while I need negative durations as well. Is there a reason why Duration can't be negative? I guess it's because of the performance impact? I can't seem to think of any other reason why.

19:47 <JamesMunns[m]> Probably consistency with the standard library Duration: https://doc.rust-lang.org/stable/std/time/struct.Duration.html

19:47 <JamesMunns[m]> It also only represents positive durations

19:48 <thvdveld[m]> The implementation in chrono allows negative Durations

19:49 <thvdveld[m]> I didn't look at the implementation in the standard library, should have checked there as well

21:25 <NiaLinaLunaStorm> does anyone here have experience with coldfire v1 chips? (generally not rust specific)

21:28 <NiaLinaLunaStorm> got a board with one on it and can't manage to get the debugger to flash it and the spec sheet doesn't tell me really on how to flash it either