Rfcs Alternatives

rfcs reviews and mentions

• Don't defer Close() on writable files
  7 projects | news.ycombinator.com | 8 Sep 2024

  That nobody has gone through the effort of collating its requirements and writing an RFC after https://github.com/rust-lang/rfcs/pull/770 was closed (back in 2015).

  I assume a big issue is that this is full of edge cases up the ass, and the value is somewhat limited in the sense that if you know you want durable writes you'll sync() and know you're fucked if you get an error, but close() does not guarantee a sync to disk, as the linux man page indicates:

  > A successful close does not guarantee that the data has been successfully saved to disk, as the kernel uses the buffer cache to defer writes.

• An Optimization That's Impossible in Rust
  2 projects | news.ycombinator.com | 4 Sep 2024

  I never heard of "German strings" in place of the small string optimization before! And there had been way too many proposals to add such types to the standard library [1] [2] [3] [4]. My understanding is that:

  1. Both `Vec` and `String` should share the same layout as part of the standard library's contract.

  2. Unlike `String`, the equivalent optimization for `Vec` is more questionable especially when T might be any type. C++ standard libraries frequently do implement multiple layouts for std::string but not for std::vector for the same reason.

  3. Rust never allows an implicit copying of `String` in the first place, which greatly benefits from the SSO, so the lack of SSO in Rust is less important compared to C++.

  [1] https://github.com/rust-lang/rust/issues/4991

  [2] https://github.com/rust-lang/rust/issues/20198

  [3] https://github.com/rust-lang/rfcs/pull/2990

  [4] https://github.com/rust-lang/unsafe-code-guidelines/issues/4...

• Async2 – The .NET Runtime Async experiment concludes
  3 projects | news.ycombinator.com | 22 Aug 2024
• Jiff: A brand new Datetime library for Rust, from the builder of ripgrep
  16 projects | news.ycombinator.com | 21 Jul 2024

  nrc was poking at the problem in 2016 https://internals.rust-lang.org/t/struct-field-defaults/3412 which led to this RFC https://github.com/rust-lang/rfcs/pull/1806

  It got postponed because it wasn't going to make it into Rust 2018: https://github.com/rust-lang/rfcs/pull/1806#issuecomment-327...

• Cultivating Open Source Community
  1 project | dev.to | 12 Jun 2024

  You can check out Rust-langs RFC Repo to see their well-documented and thorough process for an RFC.

• Generics in Rust: murky waters of implementing foreign traits on foreign types
  2 projects | dev.to | 3 Jun 2024

  Finally, I found the answer in the RFC Book (RFC stands for Request For Comments). RFC 2451 from 2018-05-30 that starts with the following lines:

• Ask HN: What April Fools jokes have you noticed this year?
  1 project | news.ycombinator.com | 1 Apr 2024

  RFC: Add large language models to Rust

  https://github.com/rust-lang/rfcs/pull/3603

• Rust to add large language models to the standard library
  1 project | news.ycombinator.com | 1 Apr 2024
• Why does Rust choose not to provide `for` comprehensions?
  1 project | news.ycombinator.com | 11 Mar 2024

  Man, SO and family has really gone downhill. That top answer is absolutely terrible. In fact, if you care, you can literally look at the RFC discussion here to see the actual debate: https://github.com/rust-lang/rfcs/pull/582

  Basically, `for x in y` is kind of redundant, already sorta-kinda supported by itertools, and there's also a ton of macros that sorta-kinda do it already. It would just be language bloat at this point.

  Literally has nothing to do with memory management.

• Coroutines in C
  4 projects | news.ycombinator.com | 25 Feb 2024
• A note from our sponsor - SaaSHub
  www.saashub.com | 4 Oct 2024

  SaaSHub helps you find the best software and product alternatives Learn more →