Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempting a fix for #140.
I queued a couple of test runs, but even though
win-windows_local.win8
was idle (which uses VS2019 v16.8.3), they all waited to run onwin-windows_nuc.win10
(which uses VS2019 v16.4.3), so I couldn't confirm that the fix works. Both CI machines seem to have the same labels, I don't know why the jobs only wanted to run on win10...CI apart, I wonder if suppressing the new warning is the correct thing to do. It feels like VS2019 is trying to tell us something and we don't want to listen 🙉