@Forkest thanks for the patch, see with enough challenging you can explain the issue clearly, why the suggested workaround doesn't work for your use-case, and provide a better workaround :)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.