> + virtual std::chrono::steady_clock::time_point time_last_buffer_acquired()
> const = 0;
>
> this makes Renderable leak the buffer stream abstraction even worse than it
> has before (I expound on this in my mp review:
> https://code.launchpad.net/~kdub/mir/produce-renderlist-for-particular-
> compositor/+merge/215052/comments/514979)
Note that the "buffer_acquired" in time_last_buffer_acquired() doesn't refer to the underlying buffer stream, but to Renderable::buffer(). That is, it returns the time point when someone last called Renderable::buffer(), regardless of the underlying implementation.
> + virtual std::chrono: :steady_ clock:: time_point time_last_ buffer_ acquired( ) /code.launchpad .net/~kdub/ mir/produce- renderlist- for-particular- +merge/ 215052/ comments/ 514979)
> const = 0;
>
> this makes Renderable leak the buffer stream abstraction even worse than it
> has before (I expound on this in my mp review:
> https:/
> compositor/
Note that the "buffer_acquired" in time_last_ buffer_ acquired( ) doesn't refer to the underlying buffer stream, but to Renderable: :buffer( ). That is, it returns the time point when someone last called Renderable: :buffer( ), regardless of the underlying implementation.