deprecating copy construction and assignment

Actually, no (if I understand your question correctly) - a deleted move constructor doesn’t cause copy construction to be used in the same context - it causes move construction attempts to produce compilation errors. Think of deletion as a nicer form of what people use to disable copy construction in c++98 by declaring but not defining the copy constructor