Unused druntime code: Barrier, ReadWriteMutex, Condition

[Dejan Lekic]

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.