5 ms·

They should probably change their terminology away from "RFC" for referring to Rust RFCs rather than IETF ones. Maybe RRFCs or REPs something? In this document

They should probably change their terminology away from "RFC" for referring to Rust RFCs rather than IETF ones. Maybe RRFCs or REPs something? In this document is a perfect example of the problem, they list several Rust RFCs by RFC number, then talk about IP RFC based loopback detection, expecting everyone to know that RFC 6890 refers to an IETF one and not a Rust one. I mean, most of us can infer that just by length of the number, but it is pretty ambiguous especially when they're used in the same document like this.

otoburb 11y ago
I have the same thought running through my head while perusing each Rust announcement. Python has the Python Enhancement Proposal[1], and Bitcoin has their Bitcoin Improvement Proposal[2]. On the flip side, this does have the side effect of forcing me to click through to each Rust RFC linked in the announcements just to be sure. [1] https://www.python.org/dev/peps/ https://www.python.org/dev/peps/ [2] https://github.com/bitcoin/bips https://github.com/bitcoin/bips
- zanny 11y ago
  RIP in peace! (Rust Improvement Proposal)
blktiger 11y ago
Ember.js uses a similar naming convention. I'm not sure that it's that important to distinguish from IETF RFCs. Especially since the RFCs are linked in that document.
sambe 11y ago
I always thought RFC was generic (and/or predates IETF). Is that not true?
- wyldfire 11y ago
  It is generic and does predate IETF but it's ambiguous to which reference material if the number ranges intersect.
- shmerl 11y ago
  It is generic. IETF's RFCs are only one example.
kibwen 11y ago
I'm fine with projects locally using "RFC" for their own purposes, but you're correct in that once you start referring to other concepts with the same initialism one should explicitly say "IETF RFC". Namespacing matters. :)
mappu 11y ago
PHP uses the RFC terminology itself, too.
derefr 11y ago
Rather than changing the name (and then me having no idea what a PEP or BIP or whatever is until I look it up—not a good way for a piece of language to work), I'd suggest namespacing the number. "RFC rust/1386" or somesuch.

otoburb 11y ago

I have the same thought running through my head while perusing each Rust announcement. Python has the Python Enhancement Proposal[1], and Bitcoin has their Bitcoin Improvement Proposal[2]. On the flip side, this does have the side effect of forcing me to click through to each Rust RFC linked in the announcements just to be sure. [1] https://www.python.org/dev/peps/ https://www.python.org/dev/peps/ [2] https://github.com/bitcoin/bips https://github.com/bitcoin/bips

zanny 11y ago
RIP in peace! (Rust Improvement Proposal)

blktiger 11y ago

Ember.js uses a similar naming convention. I'm not sure that it's that important to distinguish from IETF RFCs. Especially since the RFCs are linked in that document.

sambe 11y ago

I always thought RFC was generic (and/or predates IETF). Is that not true?

wyldfire 11y ago
It is generic and does predate IETF but it's ambiguous to which reference material if the number ranges intersect.
shmerl 11y ago
It is generic. IETF's RFCs are only one example.

kibwen 11y ago

I'm fine with projects locally using "RFC" for their own purposes, but you're correct in that once you start referring to other concepts with the same initialism one should explicitly say "IETF RFC". Namespacing matters. :)

mappu 11y ago

PHP uses the RFC terminology itself, too.

derefr 11y ago

Rather than changing the name (and then me having no idea what a PEP or BIP or whatever is until I look it up—not a good way for a piece of language to work), I'd suggest namespacing the number. "RFC rust/1386" or somesuch.