Tom Scogland

Is the ask specifically for a `reshape` that changes size, or also for the case of a `reshape` with new extents but same backing storage? The latter actually seems vaguely...

> They definitely want that. Did you have something in mind other than just `mdspan{existing_backing_storage, new_extents}` plus error checking? Essentially that but maybe as a move constructor only? That would...

Yup, sounds right @mhoemmen. (1) is right out, (2) is mainly what I was thinking, though having a way to get an mdspan from an mdarray in a manner similar...

We actually have had user requests to be able to early-release parts of their allocations also. A bit of a refactor is needed, but we need this for elasticity _and_...

Thanks @grondo, agreed there would be more work to do for eager release. I meant to look at the fluxion side, though at first glance I need to work through...

Thanks both of you, that's very helpful. They're all registered in qmanager.cpp, it's a bit tangled but now that I know where the root is it's much easier to follow.

Small clarification, the CTAD is mostly fine, it's just in copy deduction that we have problems. In this example it's specifically the `camp::tuple c = a + b;` line. Changing...

In C++20 it could literally be a std::string parameter, but I think for our current targets it would have to be a `const char *` parameter.

Yeah, agreed, thanks for the triage @garlick. I think something like this would be useful, but the "right" approach would be to hack in the "get a pollable fd from...

Just realized this is still pending, did a rebase to bring this up to date, cleaned up the one conflict. Hopefully this will pass through now.