You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling 'a Lwt.ts threads causes a lot of confusion for beginners, who mistake Lwt threads for system threads, or at least expect aspects of system thread behavior. Many examples can be cited.
I think we should just use the common terminology of the day, and call Lwt a (monadic) promise library. We should completely eliminate all mention of threads outside of Lwt_preemptive or discussion of internals of Lwt_unix.
I would mind this when fixing/rewriting the docs.
Opinions welcome.
The text was updated successfully, but these errors were encountered:
I think this is sufficiently addressed by the recent lwt.ml rewrite (#354) and lwt.mli rewrite (#469) to justify closing this issue. The remaining modules still use the term "thread," but they will be corrected soon.
Calling
'a Lwt.t
s threads causes a lot of confusion for beginners, who mistake Lwt threads for system threads, or at least expect aspects of system thread behavior. Many examples can be cited.I think we should just use the common terminology of the day, and call Lwt a (monadic) promise library. We should completely eliminate all mention of threads outside of
Lwt_preemptive
or discussion of internals ofLwt_unix
.I would mind this when fixing/rewriting the docs.
Opinions welcome.
The text was updated successfully, but these errors were encountered: