-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Keyword table in the manual uses a bizarre, change-hostile format #1216
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
Comments
This gist was used to sort those. https://gist.github.com/1330076 |
I see. A system that requires a 100-line script to update a table still seems a bit clunky. |
I didn't automated this whole thing yet, wasn't expecting keywords change soon then. I still find the resulting table in column-major ordering appealing. |
lht
added a commit
to lht/rust
that referenced
this issue
Nov 23, 2011
Keywords are now listed in a plain text file. They're sorted in column-major order and rendered as a texinfo multitable in rust.texi. Fixes issue rust-lang#1216.
Now it's automated by commit b98ef18. |
marijnh
pushed a commit
that referenced
this issue
Nov 23, 2011
Keywords are now listed in a plain text file. They're sorted in column-major order and rendered as a texinfo multitable in rust.texi. Fixes issue #1216.
Thanks! |
This was referenced Jul 14, 2016
bjorn3
added a commit
to bjorn3/rust
that referenced
this issue
Feb 23, 2022
…times Refactor the intrinsics module for slightly better build times
coastalwhite
pushed a commit
to coastalwhite/rust
that referenced
this issue
Aug 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See https://github.com/graydon/rust/blob/master/doc/rust.texi#L618 . The table is sorted column-first, and written row-first. Unless there is some tool to reorganize these that I don't know about, changing this table seems to involve manually re-sorting the whole thing, manually splitting it back into rows, and interleaving the sorted words in such a way that they align. No one should have to deal with that.
The text was updated successfully, but these errors were encountered: