-
Notifications
You must be signed in to change notification settings - Fork 43
Update for lwt 4.0.0 #63
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
Conversation
|
I don't think introducing core_kernel is possible (or even desirable). The breaking change should be towards making the hooks abstract IMO. The other changes are fine. |
|
Is it license issue? Could you please elaborate? |
|
It's a huge dependency that's being acquired for a data structure that's quite easy to implement. In particular, I'm not sure how portable core_kernel is on windows. Why not just inline some simple implementation into the source and keep it abstract? To prevent issues such as this happening in the future. |
|
Thanks, that's a step in the right direction. A few points:
We can see that the callbacks module only after adds on the left of this list. If we're going to make a breaking change, why not make something more future proof: type switch
type 'a callbacks
val create : unit -> 'a callbacks
val fold_left : ('acc -> 'a -> 'acc) -> 'a callbacks -> 'acc -> 'acc
val register : switch option -> 'a callbacks -> 'a -> unit
val exec_callbacks : ('a -> unit) callbacks -> 'a -> unit
val exec_filters : ('a -> bool) callbacks -> 'a -> boolIt doesn't seem like the |
|
I don't think it is easy to get away with a singly-linked list. The register registers a callback of remove. |
|
Okay, I see. So we'll have to keep the dlist under the hood. |
… camomile >= 1.0.0
…acks and create () in LTerm_widget_callbacks
|
To fix #60 |
|
This PR looks ready. I'm merging it and doing a release since it's blocking |
|
And thanks for this PR! |
Using core_kernel.Doubly_linked and lwt_log.