Conversation
|
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 registrationPlease make sure that you have read the package naming guidelines. 2. AutoMerge Guidelines are all met! ✅Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed. 3. To pause or stop registrationIf 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 Tip: You can edit blocking comments to add |
|
The name similarity for this is a false positive, and I can override it, but (without having looked at in in any detail) I might be a little bit concerned about potential name clashes, type piracy, or similar issues, in relation to existing packages. I’m not even quite sure how to evaluate these concerns for macros… Are these features that would potentially better contributed to the existing packages? Is this more of a “personal utility” collection (which shouldn’t go in the General registry)? It might be good to invite some community feedback on this package by posting on Discourse or Slack before continuing with the registration |
UUID: e6b49e76-7649-4be4-a64f-e8c00c6006ac Repo: https://github.com/TyronCameron/Chainables.jl.git Tree: 1d26ff292a79136219dd74a9c8b70e468b58cf62 Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
d393c2b to
9923365
Compare
|
Fair point -- thanks for the suggestion. I've opened a thread on Discourse to gather some community feedback before continuing with registration: https://discourse.julialang.org/t/seeking-feedback-on-chainables-before-registering-it/136175 |
|
Feedback (here and on Discourse) is very welcome! On the technical side: the macros just adjust the order of the arguments going in so shouldn't cause type piracy. I'm not aware of another package that does a similar thing (except perhaps |
Uh oh!
There was an error while loading. Please reload this page.