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
{{ message }}
This repository was archived by the owner on Sep 30, 2020. It is now read-only.
Feature request: either rendered text of, or short-links to the rendered text of, accepted RFCs would be nice to have somewhere on rlo where the URLs can be shorter.
For example, rustc's diagnostics has some explanations that benefit from references out to an RFC; however, the current 'canonical' URLs for RFCs (the Github renderings) are longer than the prescribed 80-character limit, which is an error.
Perhaps something like doc.rust-lang.org/rfcs/NNNN, which either presents a rendering of the RFC formatted to be consistent with the rest of the Rust documentation, or which redirects to the Github rendering of the RFC?
Concretely, instead of requiring references to variable-length URLs like (the 102-character-long)
I really like this idea. It would definitely make referencing the RFCs elsewhere easier, and I think make them more accessible to people. What sort of setup is needed to make this happen?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature request: either rendered text of, or short-links to the rendered text of, accepted RFCs would be nice to have somewhere on rlo where the URLs can be shorter.
For example, rustc's diagnostics has some explanations that benefit from references out to an RFC; however, the current 'canonical' URLs for RFCs (the Github renderings) are longer than the prescribed 80-character limit, which is an error.
Perhaps something like
doc.rust-lang.org/rfcs/NNNN
, which either presents a rendering of the RFC formatted to be consistent with the rest of the Rust documentation, or which redirects to the Github rendering of the RFC?Concretely, instead of requiring references to variable-length URLs like (the 102-character-long)
we consistently have 35 characters like
The text was updated successfully, but these errors were encountered: