Rfcs Alternatives

Posts

• 2 forms of specifying bounds in generics
  reddit.com/r/rust | 2021-01-24

  In addition to what has been said, the first syntax isn't supported on very old versions of Rust. https://github.com/rust-lang/rfcs/blob/master/text/1951-expand-impl-trait.md lists some motivations about why both options exist.

• Why is 'nightly' build so important for much of the Rust ecosystem?
  reddit.com/r/rust | 2021-01-20

  Here's the full justification for the Never Type: https://github.com/rust-lang/rfcs/blob/master/text/1216-bang-type.md

  reddit.com/r/rust | 2021-01-20

  The RFC has the reasons: https://github.com/rust-lang/rfcs/blob/master/text/1216-bang-type.md

• Unconditional loops are unconditionally awesome
  reddit.com/r/rust | 2021-01-18

  As a final thing, loop is useful as the simplest form for explaining things, like how one explains ? by talking about the match you could write instead. (See the dialectical ratchet.)

• A single issue with Rust that kills me every time with mathematics (rust repo issue 20671)
  reddit.com/r/rust | 2021-01-17

  The definitive solution will probably come when RFC 2089 (implied_bounds) will be implemented. I think the necessary work has already be done in chalk, so you'll probably just have to wait until chalk will be fully integrated in rustc (don't quote me on that though).

• Blog post: Future::join and const-eval
  reddit.com/r/rust | 2021-01-17

  There have been a few Pre-RFCs and at least one actual RFC about varidic generics by the way, just none that looked very realistic (IMHO). Here's the first one I found in my browser history: RFC2775.

• Would Rust Secure Curl?
  news.ycombinator.com | 2021-01-16

  2. Calling composition less powerful than inheritance could be seen as subjective and debatable. I mostly like composition over inheritance, but Rust for example has problems with up-casting of trait objects (https://github.com/rust-lang/rfcs/issues/2765) that inheritance/vtable based languages (e.g. C++) do not have.

  So it's not a bad comment, and I suspect you mostly just got piled on due to human bias. Or maybe some poor soul got confused and thought you were trying to explain Rust to the poster above you (who may not need much explaining).

• Would Rust secure cURL?
  reddit.com/r/programming | 2021-01-16

  That’s not true, rust has this exact feature

  reddit.com/r/programming | 2021-01-16
• Associated Types - A Bit of clarity (I think)
  reddit.com/r/rust | 2021-01-16

  This intuition is incorrect, and imo bordering on misinformation. Associated types are generics. They just set your type parameter at a different point in time. But you can talk about an associated type generically much the same way you can a type parameter, which is not the same for a type alias. For example I could write a constraint I::Item: Clone + Debug or what have you. This will only grow more true once generic associates types land on stable.

• Which sorting algorithm did you implement in your programming language?
  reddit.com/r/ProgrammingLanguages | 2021-01-13

  sort_unstable is a pattern-defeating quicksort (https://github.com/orlp/pdqsort) added with RFC#1884 (https://github.com/rust-lang/rfcs/pull/1884).

• Deprecate the Authors Field
  news.ycombinator.com | 2021-01-13
• What does it mean to be an object-safe trait?
  reddit.com/r/rust | 2021-01-12

  Other sources to check out: the reference and rfc

  reddit.com/r/rust | 2021-01-12

  rfc

• Hey Rustaceans! Got an easy question? Ask here (2/2021)!
  reddit.com/r/rust | 2021-01-11

  There's #![feature(specialization)] which allows you to give different implementations that would be picked depending on which traits the type parameter implements. However, it's nowhere near stabilization and definitely should not be used for cases like this (yet).