It was because postblit was riddled with problems... (maybe there's a lesson there?)

Anyway, I thought of an issue with separating the constructor into a bespoke name; what happens when you do this: 

=this(S);

this(S);

Which is selected? 

What about:

=this(S);

this(T)(T); which overlaps the concrete case?

This questions also exist in today's language with copy constructors, but the rules are clear; regular overload selection semantics.

Selecting the proper function to call is a task for overload resolution, not something weird and special.

If it behaves different than the way you manage the situation based on regular overload resolution regarding copy constructors, you're just asking for a raft of special-case related bugs that follow, and suffer more annoying edge cases which have to be manually identified and managed by the user.

We need to see the ways that hit dead-ends on the paths you explored.

I want to see the cases that lead to infinite recursions...