00:00 <re_irc> < (@9names:matrix.org)> You can actually buy 32bit micros, too. Rp2040 has been in stock practically the whole duration of the shortages.

00:00 <re_irc> And the other mcu vendors appear to be catching up with demand too

00:00 <Lumpio-> There used to be micros with built in CAN transceivers but unfortunately they were lost to the great chip shortage of 2020

00:01 <re_irc> < (@9names:matrix.org)> Yeah damn automotive industry

00:06 <re_irc> < (@halfbit:matrix.org)> 2020 going on 2023

00:09 <re_irc> < (@halfbit:matrix.org)> 25 in stock at mouser, https://www.mouser.com/ProductDetail/NXP-Semiconductors/LPC11C22FBD48-301?qs=fhAOlxDPaYUfq1Povfl6jg%3D%3D

01:08 <conplan> is there any way we can enable certain code for debug only

01:15 <re_irc> < (@orclev:matrix.org)> hmm, maybe "#[cfg(debug_assertions)]"?

01:16 <conplan> thanks ill try that

01:18 <re_irc> < (@orclev:matrix.org)> only problem I can see is that's enabled when compiling without optimizations, and it's pretty common to enable optimizations even when doing debug builds since space is at such a premium

01:18 <re_irc> < (@orclev:matrix.org)> for reference: https://doc.rust-lang.org/reference/conditional-compilation.html#debug_assertions

01:49 <re_irc> < (@9names:matrix.org)> If you want more control, #[cfg(feature)] works pretty well

01:50 <re_irc> < (@orclev:matrix.org)> yeah, that's the other option, declare a debug feature (or you know, give it a better name)

02:15 <re_irc> < (@firefrommoonlight:matrix.org)> Lumpio-: Is that teh part that converts 0-3.3v to the differential thing can uses?

02:55 <re_irc> < (@9names:matrix.org)> yep. integrated CAN controller + transceiver, so you don't require any external hardware (except termination resistors) to talk on a CAN bus. the NXP chip that Tom linked is such a device.

03:12 <re_irc> < (@firefrommoonlight:matrix.org)> Thx!

18:14 <re_irc> < (@orclev:matrix.org)> So, question that isn't _technically_ about embedded Rust, but is adjacent to it. I've got a macro crate I want to use, but it isn't declared no-std, but all the macros just output variants of "const &str" (they're all string literals). It doesn't seem like there's a way to actually use the crate though without forking it and slapping "#![no_std]" into it. Is there any other way of doing this or is the...

18:14 <re_irc> ... only option to modify the macro crate?

21:25 <re_irc> < (@chemicstry:matrix.org)> : If it's a proc macro, then it is okay if it uses std. If it is macro reexport or a declarative macro then you will have to add "#![no_std]". Is adding that a big problem though? Most maintainers are happy to accept PRs

22:30 <re_irc> < (@orclev:matrix.org)> : It looks like it's not _technically_ a proc macro. Apparently the authors used something called proc_macro_hack which if I'm understanding what the crate says is to add support for proc macros to versions of Rust between 1.31 and 1.45. I forked the library and added the no_std declaration as well as made a entry on their issue tracker to get that change merged in. I was just hoping there was a way to do...

22:31 <re_irc> ... this without modifying the library itself since then I could just use the version off crates.io rather than needing to pull in my fork.