[Issue 22239] Can't migrate from postblits if they are used without frame pointer

[d-bugmail at puremagic.com]

https://issues.dlang.org/show_bug.cgi?id=22239

Jonathan M Davis <issues.dlang at jmdavisProg.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |issues.dlang at jmdavisProg.co
                   |                            |m

--- Comment #5 from Jonathan M Davis <issues.dlang at jmdavisProg.com> ---
When trying to add a copy constructor to a type in an existing code base, I've
been seeing a lot of errors about not having a frame pointer (particularly from
std.algorithm code), which has been incredibly annoying to deal with, and it
has made no sense to me that a frame pointer would even be needed, since the
only difference is that a copy constructor has been added (though honestly, the
whole frame pointer stuff is incredibly confusing in general). So, I'm
_guessing_ that this is the issue that I've been hitting, but man, it would be
nice if the compiler didn't decide that it needed a frame pointer that it can't
have just because a type that's involved got a copy constructor added to it.

--