Kevin Matthes

It seems as if the softlink would be included into the build routine in a way which makes a future removal a bit complicated. I would like to suggest to...

We can create such a documentation very easy with `pandoc`. We would just need to add the concerning build instructions and experiment with the optimal set of options. `pandoc` is...

As far as I can see, this would just require further build instructions. We could instruct the CI to execute a certain build command which not only depends on the...

How about automatically uploading the documentation in a pre-compiled / self-compiling form into a separate repository within the NFFT namespace? Or into the wiki section of this repository? For instance,...

In my opinion, it is definitely an interesting feature to have an alternative build system in case that the current one, `automake`, should not be available for some reasons on...

When we would outsource both build routines to different repositories within the NFFT namespace -- and bind both as submodules --, users could decide for one during the cloning process...

By the way: the changelog format of the named crate would be also interesting for the Zee repository since it applies a well-readable community standard. I would like to suggest...

As far as I know, the Rust `sysexits` crate works on Windows fine, as well. So portability is not a problem. Mapping errors can be done by assigning the exit...

Solely the CRLF cause this behaviour. The simplest way to fix this bug is to save the opened buffer once. This will crop all CRLF. Although I have no problem...

I agree that the string conversion is not optimal but I still think that an iterator approach should at least be tested since I expect the Rope queries to be...