On Thu Apr 16 22:23:26 2026 +0000, Francis De Brabandere wrote:
scratch that, the optimization only appears when stack on top of the previous commit. @jacek Want me to push this through one MR per commit at a time? So I can show with benchmarks what each change brings? In general, I prefer keeping related commits grouped in MRs. Having many small MRs with various dependencies or conflicts makes things harder to track, so keeping a few commits per MR is usually the best approach.
In this particular case, moving the more controversial parts of this MR, namely the SAFEARRAY special case and global code handling, out of this MR would help move it forward, so that seems reasonable. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10515#note_136766