Jonathan Wakely

I only have access to one machine right now but I'll test it ASAP (probably at the weekend)

> mallinfo() and mallinfo2() are present in most libc malloc implementations. Is that true? No modern BSD seems to have either of them. Solaris, AIX and HP-UX have mallinfo but...

That still uses the move constructor.

I don't know what you mean by "in error to call out this case a violating R.5 for an initializer?" As I said above, "using an initializer" doesn't mean anything...

> I wouldn't have guessed that could help, given the message. But thanks for the workaround anyway! The way I interpret the message is that is's saying that you _should_...

Also reported as https://github.com/llvm/llvm-project/issues/118539 and https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117905

https://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0571r2.html proposes that the type of the intermediate value (`init`) needs to be both _Cpp17MoveConstructible_ and _Cpp17MoveAssignable_. Although that paper seems to be stuck in limbo (https://github.com/cplusplus/papers/issues/546) I think its...

Oh wow, yes, that completely fixes it. `GVIM_ENABLE_WAYLAND=1 gvim` works fine and can be resized.

With the environment variable set, resizing the gvim window prints these errors to the terminal: ``` (gvim:758888): Gdk-WARNING **: 14:25:03.223: gdk-frame-clock: layout continuously requested, giving up after 4 tries (gvim:758888):...

> With the environment variable set, resizing the gvim window prints these errors to the terminal: > > ``` > (gvim:758888): Gdk-WARNING **: 14:25:03.223: gdk-frame-clock: layout continuously requested, giving up...