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

async-await keywords are not documented in the libstd docs #66909

ultrasaurus opened this issue Nov 30, 2019 · 4 comments


Copy link

@ultrasaurus ultrasaurus commented Nov 30, 2019

I have a PR for this, just opening an issue, since I might be missing other parts of it.

I couldn't find up-to-date docs on the new async / await keywords. Std library docs have blank pages:

Perhaps there are other docs somewhere, but I thought to look at the RFC. The tracking bug is closed, but the RFC is not fully implemented.

ultrasaurus added a commit to ultrasaurus/rfcs that referenced this issue Nov 30, 2019
This RFC isn't fully implemented, but tracking bug is closed. 
This PR adds a tracking bug I found for part of the RFC that is not implemented.
There may be other open tracking bugs. This PR is intended to be an improvement,
may not be a complete fix for issue:  rust-lang/rust#66909
@nikomatsakis nikomatsakis changed the title async_await RFC is not fully implemented, but tracking issue is closed async-await keywords are not documented in the libstd docs Dec 3, 2019

This comment has been minimized.

Copy link

@nikomatsakis nikomatsakis commented Dec 3, 2019

@ultrasaurus did you say you have a PR for adding the docs? Good catch, I wasn't aware of that documentation.

I've retitled this to suggest the specific oversight, and I'm tagged as "on deck" as it seems worth fixing (and not very difficult).


This comment has been minimized.

Copy link

@ultrasaurus ultrasaurus commented Dec 3, 2019

@nikomatsakis I made a super simple PR to RFC repo (rust-lang/rfcs#2828) that hasn't been reviewed yet.

I'm still working my way through the docs on async / await and am not the one to judge whether the docs in nightly are ready to be merged, just flagging that async / await are now in stable ... was it an error that docs weren't merged? if intentional, then a link to nightly docs and/or RFC would be great.


This comment has been minimized.

Copy link

@nikomatsakis nikomatsakis commented Dec 7, 2019

@ultrasaurus I see. OK, I've closed that PR since that's not our usual procedure. This is a fairly minor matter from what I can tell, I thnk we mostly would want to include some text and link to the docs in the reference for more details. (I don't think the nightly docs or RFC are especially relevant to link to.) The real question is where in the source code you go to add documentation on keywords -- probably @GuillaumeGomez would be able to answer that question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.