-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kernel: Add behaviour to define callbacks for via registries #1982
base: master
Are you sure you want to change the base?
kernel: Add behaviour to define callbacks for via registries #1982
Conversation
I'm sorry for the delayed handling of this PR, and unfortunately I still have no answer. We need to discuss the way forward for behaviours in general before we can decide anything on this. Thanks for you contribution! |
@sirihansen thanks for the update! Is/Will this conversation be public. If so, where? |
At least as a start it will be an internal discussion, but we might involve the community at a later stage. If so, it will probably be on the erlang-questions mailing list. |
CT Test ResultsTests are running... https://github.com/erlang/otp/actions/runs/6500041326 Results for commit c251c30 To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts
// Erlang/OTP Github Action Bot |
@sirihansen Any update on this PR? It's the 5 year anniversary of it being submitted 🎉. |
This new behaviour defines the three callbacks required for custom registries (i.e.
{via, Module, Name}
).If accepted, and once added to bootstrap, a second PR will be added to add this behaviour to
global
.