2 Jun
2023
2 Jun
'23
5:17 p.m.
On Fri Jun 2 15:38:26 2023 +0000, Alexandros Frantzis wrote:
Seems very sensible. I will move to a more traditional/explicit locking pattern, getting rid of `wayland_win_data_release()` completely and making `wayland_win_data_get()` not perform any internal locking. For example for the data creation could look like (in pseudo-code) : ```c lock; if (!get && !create) { unlock; return; } ... unlock; ``` Let me know if you had some other approach in mind. Sure. You can also keep the internal locking, as it may be more convenient, as long as `create` checks first if is has been beaten to it.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/2944#note_34463