Unused druntime code: Barrier, ReadWriteMutex, Condition

[Richard (Rikki) Andrew Cattermole]

On 16/06/2026 9:54 PM, Dejan Lekic wrote:
> On Monday, 15 June 2026 at 23:50:01 UTC, Richard (Rikki) Andrew 
> Cattermole wrote:
> 
>> To move it requires breaking user code, and that is not an option.
> 
> Why not do what we typically did in the past - mark it deprecated with 
> message that we are not deprecating it but actually moving somewhere 
> else, and then after few months actually do it?
> 
> Instead of repeating C++ mistakes, let's not fear breaking changes, and 
> learn how to do them the right way... - If something is marked as 
> deprecated with appropriate message for 6 months those who complain 
> about broken code after that period, when the move actually happened 
> should just, put it bluntly, shut the heck up.

1. It would need to be more like 6 years, not 6 months with such long 
release cycles.

2. There is nothing actually wrong with the code, it is working correctly.

3. All multi-threaded OS's should support these primitives.

4. There are alternatives to breaking code that are a better choice.

There is a time and a place to break code, this isn't it.