New package: JiL v0.1.0

[JuliaRegistrator]

• Registering package: JiL
• Repository: https://github.com/aptmcl/JiL.jl
• Created by: @aptmcl
• Version: v0.1.0
• Commit: 7b1030b079d7f1b8976acb428921607b6e138f47
• Reviewed by: @aptmcl
• Reference: aptmcl/JiL.jl@7b1030b#commitcomment-149868785
• Description: The JiL programming language: a Lisp dialect on top of Julia.

[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

• Package name similar to 18 existing packages.

  Similar package names

  1. Similar to Jin. 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. Normalized visual distance 1.88 is at or below cutoff of 2.50.
  2. Similar to ISL. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  3. Similar to JLD. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  4. Similar to Bio. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  5. Similar to Air. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  6. Similar to GSL. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  7. Similar to Git. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  8. Similar to VSL. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  9. Similar to JDF. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  10. Similar to LSL. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  11. Similar to Jive. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  12. Similar to HSL. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  13. Similar to JOLI. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  14. Similar to JET. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  15. Similar to XML. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  16. Similar to MKL. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  17. Similar to QML. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  18. Similar to KML. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

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.

[goerz]

For this type of package, I think a name like JiL should be fundamentally okay. However, you'll have to convince a registry maintainer to merge it manually. Since names like JiL are somewhat scarce, it is probably much easier to do this if the project is already pretty mature, with full documentation, and there's some community discussion about it. Maybe it would be good to make some kind of "pre-announcement" on Discourse to introduce the package and explain your background and motivation for developing this