Brad Richardson

> @everythingfunctional is the `type(T) :: x` inside a template effectively like a global variable, so if you do `unique`, it becomes "declared" twice (as two different variables), but without...

I'm running with: * gfortran 12.2.0, Arch Linux system supplied * openmpi 4.1.4, Arch Linux system supplied * opencoarrays 2.10.1, self-compiled The following reproducer is what led me back here:...

I did indeed come up with the initial design primarily on my own. I was trying be compatible with what I believed to be common best practice in Makefiles, but...

> Where should the build script be located within the project tree? The Haskell implementation assumed the top level of the project. I would initially lean towards that, but if...

> What happens if my project depends on two packages, which export a library with the same name? Can this cause a linking problem? > > Does the library generated...

For a one way build script, fpm wouldn't know that other libraries are produced. I'm guessing we're already including different build directories as include locations in the link commands, so...

A comment about the syntax highlighting is that (at least locally), it can be changed without too much effort to still treat `.f` as free-form Fortran. For every editor I've...

I'm not sure I'd ever expect the compilers to change their default behavior for `.f`. They have far too many existing users to support that aren't interested in updating their...

@certik , yeah, that statement was a bit hyperbolic. We do of course want to have an option to revert back to the old ways, if for know other reason...

This is an interesting idea. I would expect fpm would be a TAP consumer, but maybe it should just support TAP consumers as plugins? I also like the idea of...