New package: MallocArrays v1.0.0

[JuliaRegistrator]

• Registering package: MallocArrays
• Repository: https://github.com/LilithHafner/MallocArrays.jl
• Created by: @LilithHafner
• Version: v1.0.0
• Commit: f6bfd77055d276e14e758ea1548236ea3d89d4e7
• Reviewed by: @LilithHafner
• Reference: https://github.com/LilithHafner/MallocArrays.jl/commit/f6bfd77055d276e14e758ea1548236ea3d89d4e7#commitcomment-141376226
• Description: Back to the stone age!

[github-actions[bot]]

Your new package pull request met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

Since you are registering a new package, please make sure that you have read the package naming guidelines: https://pkgdocs.julialang.org/v1/creating-packages/#Package-naming-guidelines

---

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. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

[LilithHafner]

Hmmm. MallocArrays and AllocArrays are quite similar names.

I originally planned to name this package Malloc.jl, but then I realized that it provides the MallocArray type as its primary functionality so I renamed it to MallocArrays.jl. I'm open to Malloc.jl, MallocArrays.jl, or some other, better name someone else can come up with.

[noblock]

[goerz]

[noblock] I have no particular opinions here, although I agree that AllocArrays and MallocArrays seem a little too close for comfort. Maybe get some more eyeballs on this on Slack and/or Discourse for naming suggestions.