risa2000

@rpavlik Thanks, you answered my questions! I have just two comments. ad 1) If the runtime/compositor should not block on (possibly still being rendered) "last released" image (which makes sense),...

After some thought, I suggest that the specification makes the distinction between "last released" and "last finished" image and use the right one in the swapchain management context (going with...

I just got bitten by the same behavior when migrating from `xtensor-0.24.0` to `xtensor-0.26.0`, where it seems the define `XTENSOR_FORCE_TEMPORARY_MEMORY_IN_ASSIGNMENTS` is by default undefined. Falling back to `xtensor-0.25.0` seems to...

@gregmarr Right! A trivial overlook on my side :(. If I declare the conversions in `nlohmann` namespace it works as expected (https://godbolt.org/z/K94hcz7ja): ```c++ #include #include #include namespace nlohmann { inline...

It is basically an analogy to `std::filesystem::path`. I am not sure there is any other (sane) way how to represent it in JSON as much as there is any other...

@gregmarr I am not sure I am following you. For me `json::json_pointer` is an opaque structure, which may (in the same way as `std::filesystem::path`) have a semantical meaning (i.e. will...

I believe this has been resolved by #4631 and could be closed.