msvc
Here are 167 public repositories matching this topic...
-
Updated
Jul 1, 2020 - C++
-
Updated
Apr 29, 2020 - C++
-
Updated
Jun 13, 2020 - C
Multiple projects
I have several projects and each project has several libraries. I would like to control the license at library scale.
How should I do that? Do I need to generate one license file for each library of each project?
-
Updated
Jun 6, 2020 - Shell
-
Updated
Apr 4, 2020 - C++
-
Updated
Sep 9, 2019 - C++
-
Updated
Jul 1, 2020 - Batchfile
-
Updated
Jun 11, 2020 - C
-
Updated
Mar 16, 2020 - C
-
Updated
Apr 17, 2019
-
Updated
Jun 26, 2020 - Shell
-
Updated
May 27, 2020 - C++
-
Updated
Jun 15, 2020 - PowerShell
If users want to perform the full analysis, they have to type --analyze_all (or add as many --analyze_ options as desired).
Can't we make this flag optional, and set by default?
When users want only one part of the analysis, this flag would become disabled instead.
-
Updated
Apr 20, 2020 - C
-
Updated
Jun 14, 2020 - JavaScript
-
Updated
Jun 7, 2020 - C
-
Updated
Dec 30, 2019 - C
-
Updated
Jun 6, 2020 - Shell
-
Updated
Jun 7, 2020 - Assembly
Improve this page
Add a description, image, and links to the msvc topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the msvc topic, visit your repo's landing page and select "manage topics."
bug in README.md when_all_ready() example:
task<> example2()
{
...
// Unpack and handle each result individually once they're all complete.
for (int i = 0; i < 1000; ++i)
{
try
{
>>> std::string& record = tasks[i].result();
should be
std::string& record = resultTasks[i].result();
...
}