#Prior discussions/openness w.r.t. adjustments to OTP/Supervisor API?

1 messages · Page 1 of 1 (latest)

dense maple
#

Hi, was fiddling around with Gleam's OTP library and still have only a somewhat coarse grasp of it but would selfishly like to enable and/or facilitate some behaviour. For example, adding one_for_one and one_for_all restart strategies, and an easier way to get a list of children/subjects.

Is this something the core team would be comfortable to entertain and are there prior discussions / any pointers on where to start best? Based on this comment, I assume at least a partial yes .

I think we likely need to supervisors that implement all the different strategies, and possibly some other patterns that may be useful given Gleam OTP's lack of process naming.)

GitHub
[Feature] DynamicSupervisor please · Issue #42 · gleam-lang/otp

Hello. I think Gleam's typed OTP and its concept of subject is great. But, It would be better to have some types of DynamicSupervisor that allow me to spawn workers as I need.

#

Prior discussions/openness w.r.t. adjustments to OTP/Supervisor API?

versed flint
#

Hello! Yes we do want the other supervision strategies covered

#

I think it would be good to give the current one a specialised name too

#

rather than calling it "supervisor"

dense maple
#

Can't promise anything but will look into it.
Regarding the renaming, akin to actor instead of GenServer?

versed flint
#

As in instead of Supervisor Elixir could have DynamicSupervisor

#

We could extend that to the other strats