Closed Marioalexsan closed 6 months ago
It appears that in trying to fix this whitespace error myself then squashing the new commit that was created, I accidentally pushed these changes straight to 2.6.x. I didn't realize your PR was opened from your own repo's 2.6.x branch. I'm used to that not being the case and thus I can edit the PR's branch without affecting the target branch. Oh well. I was already going to merge it anyways so the outcome is all the same.
Thanks for your work!
Figured I might as well make an attempt at this. Not sure if
sfMalloc
is needed but I added it in for completeness.Fixes #235.