TotoGaz

@paveltomin it's not planned, but we still need to do it!

> but jury said no non-mpi! Which means that we have to properly remove the possibility to try a non-MPI build.

@CusiniM I've done all your comments.

> @francoishamon @TotoGaz or @klevzoff can you start reviewing this PR? If not, please indicate who else should review it. Thanks! Hello, as I previously discussed, we'd like this PR...

@rrsettgast @CusiniM I've used a link which is built on the fly from `.vscode-codespaces` to `.vscode`. So I think that the situation is nice now (w.r.t. conflicts with others' settings)....

@rrsettgast @CusiniM is it possible to merge this PR as is? It think there's no more conflict, and it can be used as an example on how to use `vscode`...

@XL64 Is this fixed in a more recent version of the compiler?

@XL64 Is this still relevant?

> Also this modification makes calculating the determinant significantly more costly. I'm not sure you can answer this question but maybe the kind of matrices that pop up in the...

Can you put the actual error message close to the desired error message? It's complicated to follow...