10:20 <re_irc> <9names (@9names:matrix.org)> hey folks. anyone know why embedded-sdmmc-rs release 0.4.0 never happened?

10:20 <re_irc> the pr was merged, the issue was closed, but nothing appeared on crates.io and no tag was created in the git repo.

10:20 <re_irc> https://github.com/rust-embedded-community/embedded-sdmmc-rs/issues/52

10:24 <re_irc> <9names (@9names:matrix.org)> oh it was only merged into 'develop'. i thought it made it's way to master.

10:26 <re_irc> <jannic> Also, the latest git commit was a breaking change - so in case somebody does the release now, it does make a difference if you release the commit named "Prepare 0.4.0 release" or current head. (And I'm taking about the develop branch as well, as it's the default branch of that repo.)

13:03 <re_irc> <aktaboot> thebutlah: has it been a pain to code on that thing with rust ? I have not yet used rust on esp32s, and I was wondering about the current state, especially for the risc-v thing 🤔

14:43 <re_irc> <James Munns> btw, mini announcement:

14:43 <re_irc> Decided to do a "Final Friday Showcase" on twitter, for anyone to plug their rust-embedded related work:

14:43 <re_irc> https://twitter.com/rustembedded/status/1561362532832579590

14:44 <re_irc> <James Munns> Send the RE twitter a DM with a link/picture/video and a tweet-sized description, and I'll tweet it out on Friday. I'd like to make this a success, so if any of y'all have something to share, I'd really appreciate it :D

14:45 <re_irc> <James Munns> If you don't have twitter, you can DM me on matrix, and I'll add it to the queue :D

20:14 <re_irc> <eldruin> jannic: Ah, thanks for noticing! I'll take the commit into the release, since it is a breaking one anyway and I never released it

20:14 <re_irc> <eldruin> 9names: Sorry about that, I forgot to publish it

20:19 <re_irc> <jannic> eldruin: I'm not sure if the commit should be part of the release. It might not have been intentional to make it a breaking change.

20:20 <re_irc> <eldruin> ok I'll publish as-is then and we will see on the next release

20:23 <re_irc> <jannic> As noticed here (https://github.com/rp-rs/rp-hal/pull/426#discussion_r950879789), it's a subtle property of type inference that the default parameters are not considered in this case. I don't know if ostenning really wanted to change the API so that the caller has to specify those values manually. Kind of defeats the idea of default parameters.

20:24 <re_irc> <eldruin> ok, I'll wait with the release

20:24 <re_irc> <eldruin> I have another fix PR was well https://github.com/rust-embedded-community/embedded-sdmmc-rs/pull/58

20:27 <re_irc> <jannic> Fine. I guess nobody is urgently waiting for the release, otherwise it would have been noticed earlier that it never got published.

20:30 <re_irc> <eldruin> Could you open an issue for the problem you discovered in the embedded-sdmmc-rs as well?

20:30 <re_irc> <eldruin> It would be good to assess that before making a new release

20:41 <re_irc> <jannic> https://github.com/rust-embedded-community/embedded-sdmmc-rs/issues/61

20:44 <re_irc> <jannic> I personally don't have a use case for that crate, I just stumbled upon the build failure in "rp-hal". So I don't know how it is usually used and if this change is actually an issue or if it's sufficient to just adapt the docs to state that those values need to be specified.

21:01 <re_irc> <eldruin> yeah probably just documenting it is fine. Thank you!

23:51 <re_irc> <adamgreig> dirbaio: I wonder if the singleton macro should actually be in critical-section or something, it's no longer cortex-m specific at all...