strip synstructure consts from compiler docs #60885
That seems inconsistent to me. I agree that in the majority of cases, underscore consts would be private, so they would be ignored by rustdoc. But what if `--document-private-items` is used or if the const is `pub`? What if the const has a doc comment?…
On Thu, May 16, 2019, 4:43 PM Mazdak Farrokhzad ***@***.***> wrote: @euclio <https://github.com/euclio> That's not my assumption; underscore consts are sort of explicitly for the purpose of "ignore me please I just want a gensym". — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#60885?email_source=notifications&email_token=AAKPCFS4U6Q6KUF6UZQFCCDPVXBPPA5CNFSM4HNPIVS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVTAFIQ#issuecomment-493224610>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKPCFVC2UDKLI3KJF2JOFTPVXBPPANCNFSM4HNPIVSQ> .
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews.