New package: AbstractNFFTs v0.1.0

[JuliaRegistrator]

• Registering package: AbstractNFFTs
• Repository: https://github.com/tknopp/NFFT.jl
• Created by: @tknopp
• Version: v0.1.0
• Commit: e07b474d87e73187d61281b86e967355ae8a4848
• Reviewed by: @tknopp
• Reference: JuliaMath/NFFT.jl@e07b474#commitcomment-62792323
• Description: Julia implementation of the Non-equidistant Fast Fourier Transform (NFFT)

[github-actions]

Your new package pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

• Package name similar to 1 existing package.
  1. Similar to AbstractFFTs. Damerau-Levenshtein distance 1 is at or below cutoff of 2. Damerau-Levenshtein distance 1 between lowercased names is at or below cutoff of 1.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simple retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged.

Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

[tknopp]

[noblock] The naming distance is unavoidable. AbstractNFFTs is a sister package to AbstractFFTs but it targets the non equidistant FFT, which AbstractFFTs will not capture. The package AbstractNFFTs will allow NFFT.jl and NFFT3.jl to use a common interface.