tdm-gcc | TDM-GCC is a cleverly disguised GCC compiler for Windows | Compiler library

As the error suggests, CMake found your OpenCV installation, but it is not compatible. What is it not compatible with? Your compiler. The OpenCV installation is built with MSVC 15 (it also includes a 14 build). You have asked CMake to use MinGW as your compiler. Libraries need to have been built with the same (well, with some leeway) compiler for everything to work.

You have two options:

• Build OpenCV yourself with MinGW, or try a third-party MinGW binary distribution of OpenCV. Web searches for "opencv mingw" turn up some possibilities.
• Use the MSVC compiler for your project. Microsoft offers some free versions of its tools. Just be sure to install the optional older toolsets so that you have access to the VC 15 tools to match OpenCV.

After many tries, I find out the way of installing zmq for Go.

First of all, I tried another GCC software. Software downloaded from https://www.msys2.org/ and installed on C:\msys64.

Then add C:\msys64\mingw64\bin to PATH environment variable of the windows.

Then run the following commands one by one.

tic/toc should be fine, but it looks like the timing is being skewed by memory pre-allocation.

I can reproduce similar timings to your MATLAB example, however

• On first run (clear workspace)

  • Loop approach takes 2.08 sec
  • Vectorised approach takes 1.04 sec
  • Vectorisation saves 50% execution time

• On second run (workspace not cleared)

  • Loop approach takes 2.55 sec
  • Vectorised approach takes 0.065 sec
  • Vectorisation "saves" 97.5% execution time

My guess would be that since the loop approach explicitly creates a new matrix via zeros, the memory is reallocated from scratch on every run and you don't see the speed improvement on subsequent runs.

However, when HH remains in memory and the HH=___ line outputs a matrix of the same size, I suspect MATLAB is doing some clever memory allocation to speed up the operation.

We can prove this theory with the following test:

I think this has native Go support: https://www.example-code.com/golang/default.asp

which means, you don't have to use your way of doing this.

std::istream is written in terms of char_type being simply char, and similarly, std::istream::read is the same.

The conventional approach would be to reinterpret_cast the pointer that you are reading to:

This loop is wrong,

The command you want to build, will have to be built using a task. Once built in a task, you can then bind it to which ever key configuration you like. Before I answered this I built a simple example to help demonstrate what I just said.

Create a tasks.json file in the .vscode directory. You can use this command from your projects root:

Tasks are like creating complicated keybinding (well sort'a), its more like a complex keybinding that took steroids, and can do a bunch of stuff keybindings cannot do. All BS aside, it is an extremely powerful tool. VSCode users that are not using it, are missing out on one of the most powerful features that VSCode offers. Anyhow, this is how you create a task that, in-a-nutshell, defines and executes a shell command.

This line:

As suggested by @rustyx a computer reboot resolved the problem. I don't exactly know why a reboot is needed for VS Code debugger to work.