Chris MacMackin

@Vindaar When I tried using the `[]` operator in a place where a mutable result was needed I got a compiler-error because apparently it didn't return a mutable result. @mratsim...

Your approach to external allocators looks like exactly what I need. However, how would a user supply a custom allocator when constructing an array? I've taken a look at weave...

Custom allocators for `seqs` (and strings, for that matter) would certainly be appreciated as it would allow coarrays to work with these builtin types. Barring that, would it be possible...

> One personal challenge I have with stock Fortran are its somewhat awkward and low-level I/O facilities -- `open`, `read`, `write`, `inquire`, `rewind`, and `close`. I often wished for a...

> So here are other things that could be part of `stdlib`: > > * sparse matrices > > * fft > > * special functions (like in SciPy) such...

A bit more thought makes me wonder if it would in fact be better to do this in Fortran, as converting between Fortran and C strings is quite a painful...

@certik Yes, that's what I was thinking of, although I don't think it would be practical to allow named-arguments in the format string, given Fortran doesn't have features like that.

> Related to this is what dependencies we can have. In #10 we will have to depend on a LAPACK implementation. The reference Lapack is in pure Fortran, but we...

I'm incline to agree that it is better to use `copy.deepcopy` as it is the best practice. Given that `list` is not used anywhere else and learners are not really...

Remember, too, that the optimizations for object oriented Fortran will only improve. According to [this paper](http://airccse.org/journal/ijsea/papers/5314ijsea03.pdf) there is still some low-hanging fruit waiting to be optimized.