Should this repo be archived ?

[pwnorbitals]

There hasn’t been activity nor interest for a long time, but the description marks it as still maintained, which seems confusing. What’s the current status of this repo ?

[adamgreig]

I think in practice this can probably be replaced with critical_section::Mutex. I'll put it on the agenda for today's wg meeting.

[pwnorbitals]

(@adamgreig)

[adamgreig]

Our conclusion from the meeting was that it probably should be archived; I'll organise an RFC and vote by the resources team where we can discuss further exactly what to do.

[Altair-Bueno]

Just a heads-up, this issue wasn't updated with any link to the RFC. Any progress in this regard?

I was looking for some common abstraction for critical sections and found things like mutex-trait, lock_api and critical_section. From what I've seen, all of them fail to provide an abstraction that is widely used for both std and no_std library authors, as well as async (e.g tokio::sync::Mutexandembassy-async::mutex::Mutex`... So, how should anyone approach this issue?