Nothing exciting, just some warnings silencing.
Fixing warnings is a truly noble task, given the current broken-window nature of the VS codebase with respect to warnings :)
If enough of them go away, we might even be able to read which new ones are useful indicators that we've done something ill thought out :)
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.