Federico Perini

@jvdp1 @zoziha I've implemented a `pure subroutine` interface, that looks [like this](https://github.com/fortran-lang/stdlib/blob/316c44ad0a3a1868b9ead2596acdd6c4e4c9c231/src/stdlib_linalg.fypp#L283-L296): ```fortran call solve_lu(a,b,x,pivot=ipiv,overwrite_a=.true.,err=err) ``` - Is `solve_lu` a good name? I've chosen this because it follows the same...

This is a very interesting proposal @MilanSkocic. I have a comment that does not want to mandate any specifications, but just lay out ideas on how this could be made...

> the generic facility It's definitely useful if this class has a few methods (including a nice `print`, etc.). For the purpose of just returning the numeric value (and because...

Thanks @loiseaujc, @jvdp1 has already summarized it all. Couple comments from my side: - I've been striving to improve good `blas`/`lapack` backends, and we get nice interfaces in turn, but...

That is a great plan! Let's start parsing the `BLAS` interfaces, these are fewer and easier to start with.

Usually, a new branch is created for each PR, then is merged back into master when it is approved

I believe a great starting point would be that the preprocessing script allows both CMake and the stdlib-fpm build to achieve exactly the same output as they have now. In...

As far as I can tell, having the `[build]` structure in `fpm.toml` have one more key-value pair should not break anything, because it is not even queried in any of...

Wow, this is a pretty severe limitation. ``` [dependencies] [dependencies.toml-f] git = "https://github.com/toml-f/toml-f" rev = "aee54c5a480d623af99828c76df0447a15ce90dc" ``` But, the current fpm build points to a given commit. I guess we...

Yes I agree the major improvements planned on fpm will break many things. Let's leave this PR here for when the time comes.