Skip to content
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

Discussion: deprecate Lwt.ignore_result #359

Closed
aantron opened this issue May 18, 2017 · 3 comments
Closed

Discussion: deprecate Lwt.ignore_result #359

aantron opened this issue May 18, 2017 · 3 comments
Assignees
Milestone

Comments

@aantron
Copy link
Collaborator

aantron commented May 18, 2017

@Drup in #332 (comment):

(well, Lwt.ignore_result is also a serious anti-pattern and people should probably never use it, but that's another discussion :p)

What is the reason for that? Should it be deprecated in favor of, say, Lwt.async?

@Drup
Copy link
Member

Drup commented May 18, 2017

At the very least, I think it should be made very clear in the documentation that this function gives no guarantee whatsoever about when the ignored bit will be executed.

@aantron
Copy link
Collaborator Author

aantron commented May 18, 2017

Right, I've likewise seen usage where the user clearly meant >>= fun _ -> or >|= ignore >>= fun () -> instead.

@aantron aantron added the docs label May 18, 2017
@aantron aantron added this to the 3.1.0 milestone May 20, 2017
@aantron aantron added the easy label May 20, 2017
@aantron aantron removed the easy label Jun 1, 2017
@aantron aantron self-assigned this Jun 1, 2017
@aantron aantron modified the milestones: 3.1.0, 3.2.0 Jul 18, 2017
@aantron
Copy link
Collaborator Author

aantron commented Oct 12, 2017

This will be accomplished by #469 ("New reference docs for module Lwt"), which moves ignore_result to the very bottom of the docs, into section Deprecated, subsection Miscellaneous. It explains the reason for deprecation. It doesn't add an annotation, because I'm guessing it's not worth annoying existing users over, but I may be wrong here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants