You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#include <chrono>
#include <iostream>
#include <vector>
using namespace std;
int main()
{
int k, N = 3;
double sum = 0;
for (k = 0; k < N; k++)
{
auto t1 = chrono::high_resolution_clock::now();
//do something.
vector<int> vInt;
constexpr int vSize = 1000000;
int i;
for (i = 0; i < vSize; i++)
vInt.push_back(i);
//end.
auto t2 = chrono::high_resolution_clock::now();
chrono::duration<double, std::milli> fp_ms = t2 - t1;
sum += fp_ms.count();
cout << "[" << k + 1 << "]"
<< "The elapsed time is " << fp_ms.count() << " milliseconds." << std::endl;
}
cout << "The average elapsed time is " << sum / N << " milliseconds." << std::endl;
// system("pause");
return 0;
}
The text was updated successfully, but these errors were encountered:
Possibly variation Microsoft/vscode#67296 and Microsoft/vscode-cpptools#2998. I was able to start up vscode-cpptools debugging with "externalConsole=true" (ref #45). It works alright. However, it will only work if your remote side is set up so the external console can be launched on that side of the fence.
If something goes wrong, and the terminal can't be launched, then there isn't any feedback and it looks like "nothing happened" because vscode doesn't report any error (the symptom is usually the red debugging stop button lights up and then... nothing). Something is going to go "wrong" somewhat commonly, because the remote side isn't necessarily capable of launching a console.
Regardless of whether the behavior changes per #45 it would be nice if there was some glaring error when the external console fails to spawn for whatever reason (including locally).
When
"externalConsole"
in launch.json is set false, everythig is just ok.When set true, nothing happened.
The text was updated successfully, but these errors were encountered: