New package: Luma v0.1.0

[JuliaRegistrator]

• Registering package: Luma
• Repository: https://github.com/epilliat/Luma.jl
• Created by: @epilliat
• Version: v0.1.0
• Commit: 8bf93da7ae296cae817499bcde605ae06adc3b94
• Reviewed by: @epilliat
• Reference: Register v0.1.0 epilliat/KernelForge.jl#1

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines which are not met ❌

• Name is not at least 5 characters long
• I was not able to load the package (i.e. import Luma failed). See the AutoMerge logs for details.

3. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

4. To pause or stop registration

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.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[gdalle]

Hi, congrats on the new package! Would it make sense to integrate the new functionality into AcceleratedKernels.jl?
[noblock]

[epilliat]

Hello @gdalle

Thanks for the suggestion! I think keeping it as a separate package makes more sense for now:

• It heavily relies on KernelIntrinsics.jl, which currently only supports CUDA (while AcceleratedKernels.jl targets multiple backends)
• It's still experimental and doesn't work on views yet
• Because of this, the core kernels ended up being quite different from AK.jl's implementation.

Merging them would be a significant amount of work at this stage. Once KernelIntrinsics supports other backends and things stabilize a bit, we could definitely revisit this.

[goerz]

The name similarity seems like a false positive to me, so I've applied the override.

[noblock]

[epilliat]

Also, if you think the similarity of name is too close, I can change it to "KernelForge". This is also another name that I like for this package, maybe even better. What do you think ?