Hacker GitHub

← All repos

rust-lang/rust

View on GitHub ↗ ★ 120,971 Rust

Empowering everyone to build reliable and efficient software.

1,825 mentions on Hacker News by 819 people: 158 stories, 1,667 comments · first 2012-01-20 · latest 2026-10-22

Mentions per year 1,825 mentions · busiest year 2023 (167)
20082026
  1. …at https://en.wikipedia.org/wiki/Python_License . Similarly, the reference Rust implementation ( https://github.com/rust-lang/rust ) is licensed under Apache 2.0 and MIT licenses. In what sense is FOSS software a kind of non-FOSS software?
    comment by zahlman · 2025-06-26 · in Memory safety is table stakes
  2. Even 'git status' gets slow on large repositories (or slow hosts). git status takes 643ms for github.com/rust-lang/rust
  3. …in a well-designed way, or removed -- the current status is very unsatisfying and prone to bugs." https://github.com/rust-lang/rust/issues/48055#issuecomment-...
    comment by kibwen · 2025-06-13 · in Rust compiler performance
  4. …development might have otherwise dictated. FWIW while it was a factor it was just one of a number: https://github.com/rust-lang/rust/issues/36963#issuecomment-... And jemalloc was only removed two years after that issue was opened:…
    comment by masklinn · 2025-06-13 · in Jemalloc Postmortem
  5. OK, parser then: https://github.com/rust-lang/rust/tree/1.87.0/compiler/rustc... (main logic seems to be in expr.rs) vs https://github.com/ziglang/zig/blob/0.14.1/lib/std/zig/Parse... Again, for those who wish to form their own opinions.
    comment by AndyKelley · 2025-06-12 · in Rust compiler performance
  6. …in both Go and Rust: [Go] https://github.com/golang/go/blob/f18d046568496dd331657df4ba... [Rust] https://github.com/rust-lang/rust/blob/40daf23eeb711dadf140b... While Go leans on the enum value produced by `range` to act as the language's…
    comment by 9rx · 2025-06-10 · in Go is a good fit for agents
  7. …support for infinite loops without guaranteed forward progress, allowing this to be fixed: https://github.com/rust-lang/rust/issues/28728
    comment by kibwen · 2025-06-07 · in Low-Level Optimization with Zig
  8. …v.Close()`? In almost all cases, `close(2)` errors can be safely ignored. Rust also does this: https://github.com/rust-lang/rust/blob/792fc2b033aea7ea7b766...
    comment by database64128 · 2025-06-04 · in (On | No) Syntactic Support for Error Handling
  9. …hours ago. The entire error message was literally "operation not supported on this platform". Yeay. https://github.com/rust-lang/rust/issues/141854 > I'll also note that this was quite annoying to debug since the error message in its…
  10. It’s coming soonish! There’s an accepted RFC that’s getting close to being ready to stabilize https://github.com/rust-lang/rust/issues/132162
    comment by steveklabnik · 2025-05-31 · in C++ to Rust Phrasebook
  11. …very descriptive of what this does since the operations themselves are algebraic. Also this comment https://github.com/rust-lang/rust/issues/136469#issuecomment... > > On that note I added an unresolved question for naming since algebraic…
    comment by nextaccountic · 2025-05-31 · in Beware of Fast-Math
  12. I helped design an API for "algebraic operations" in Rust: < https://github.com/rust-lang/rust/issues/136469 >, which are coming along nicely. These operations are 1. Localized, not a function-wide or program-wide flag. 2. Completely safe,…
    comment by orlp · 2025-05-31 · in Beware of Fast-Math
  13. …use unsafe Yes it does, it uses 'stdout.write_all', which ultimately uses unsafe to call libc.write https://github.com/rust-lang/rust/blob/d76fe154029e03aeb64af... The "unsafe" in uutils is just better hidden. I personally like my…
  14. …trick ? Edit: If I had read the next paragraph, I'd have learn about [1] before commenting [1] https://github.com/rust-lang/rust/issues/140167
    comment by smallpipe · 2025-05-22 · in Improving performance of rav1d video decoder
  15. The associated issue for comparing two u16s is interesting. https://github.com/rust-lang/rust/issues/140167
  16. …loop, can quickly balloon from O(N) to O(scary). https://github.com/PSeitz/lz4_flex/issues/147 https://github.com/rust-lang/rust/issues/117545 If I'm reading that log-log plot right, that looks like a significantly worse than 100x slowdown…
    comment by MaulingMonkey · 2025-05-21 · in Writing into Uninitialized Buffers in Rust
  17. …the bug in question, it has been quite "popular" for about 5 years now, and is actively tracked : https://github.com/rust-lang/rust/issues/110338 . Nothing really weird. Just async hitting the limits of the current rust design.
  18. i didn't "find" it. As i said, it's a well known one : https://github.com/rust-lang/rust/issues/110338 Simply using axum with code using multiple layers of async was enough. But then again, it looked like this bug (the error message is the…
  19. …how useful those were. EDIT: okay, so I'm doing some digging: error codes were added before 1.0... https://github.com/rust-lang/rust/commit/0e80dbe59ea986ea53c... > This implements the minimal scaffolding that allows mapping diagnostic…
    comment by steveklabnik · 2025-05-16 · in Evolution of Rust Compiler Errors
  20. …under -used in Rust, not overused. If that does become a problem, there are also techniques like https://github.com/rust-lang/rust/issues/68262 too.
    comment by steveklabnik · 2025-05-10 · in Rust’s dependencies are starting to worry me
  21. …https://github.com/geiger-rs/cargo-geiger . The Rust compiler has some unsoundness issues such as https://github.com/rust-lang/rust/issues/84366 . Those would need fixing or linter coverage.
  22. Rust had something similar: https://github.com/rust-lang/rust/issues/13871
  23. …s.rust-lang.org/t/expose-llvms-or-disjoint-i... - https://github.com/rust-lang/libs-team/issues/373 - https://github.com/rust-lang/rust/pull/124601 Which ultimately culminated in an opinion that should sound familiar -…
  24. https://github.com/rust-lang/rust/issues/28728
  25. …and needs to be qualified. You probably noticed, but it should become a thing in RFC 3591: https://github.com/rust-lang/rust/issues/134691 So it does kind of work on current nightly: #![feature(import_trait_associated_functions)] use…
  26. …in the README seems to be outdated, there's more up-to-date progress on reproducible rustc at https://github.com/rust-lang/rust/issues/129080
    comment by csense · 2025-04-20 · in Bootstrapping Rustc from Source
  27. …blog post to compare modern typestate patterns to the historical built-in typestate mechanism. https://github.com/rust-lang/rust/issues/2178
  28. …append .patch or .diff to any PR or commit URL, and you'll get back a git-formatted patch or diff. https://github.com/rust-lang/rust/pull/139966 https://github.com/rust-lang/rust/pull/139966.patch https://github.com/rust-lang/rust/pull/1399…
  29. …is immediate: ```rs fn main() { loop {} } ``` I think this can even cause Undefined Behavior :) https://github.com/rust-lang/rust/issues/28728
  30. …to the world should have been used instead. Very very old Rust had "crate files" which were this https://github.com/rust-lang/rust/blob/a8eeec1dbd7e06bc811e5... .rc standing for "rust crate" There's pros and cons here. I'm of two minds.
    comment by steveklabnik · 2025-04-15 · in Two Years of Rust
  31. …is how you signal to the compiler that “atomically writing two values at once” might happen). https://github.com/rust-lang/rust/pull/68491
  32. Many years ago I think, here: https://github.com/rust-lang/rust/issues/46213 . (Found this via https://lobste.rs/s/w3jjb2/surprising_enum_size_optimization... )
  33. …So if it's always equal to cfg!(target_feature="v"), then what does that even mean? I have created https://github.com/rust-lang/rust/issues/139139
    comment by thomashabets2 · 2025-03-30 · in Towards fearless SIMD, 7 years later
  34. …clock is monotonic? [1] [0]: https://github.com/microsoft/TypeScript/wiki/Breaking-Change... [1]: https://github.com/rust-lang/rust/blob/e2223c94bf433fc38234d...
  35. Trait upcasting will land in Rust 1.86.0 which will be released in one week: https://github.com/rust-lang/rust/pull/134367
  36. …looks like the Rust standard library migrated away from SRWLOCK on account of this issue [0]. [0] https://github.com/rust-lang/rust/issues/121949
  37. …issue is a different, but related tracking issue. The FP-in-const tracking issue was this one: https://github.com/rust-lang/rust/issues/57241
    comment by kibwen · 2025-03-23 · in Crabtime: Zig’s Comptime in Rust
  38. …Looks like floating point math in const fn is coming. Here is the respective tracking issue: https://github.com/rust-lang/rust/issues/128288
    comment by weinzierl · 2025-03-22 · in Crabtime: Zig’s Comptime in Rust
  39. A long-standing issue with that was just recently fixed: https://github.com/rust-lang/rust/pull/133250
    comment by ofek · 2025-03-17 · in Zlib-rs is faster than C
  40. …would probably be faster thanks to the standard library sort being the fastest, across languages ( https://github.com/rust-lang/rust/pull/124032 ). Again, faster than C. Happy to give more examples if you’re interested. There’s nothing…
    comment by nindalf · 2025-03-16 · in Zlib-rs is faster than C
  41. …library has a state of the art sort implementation. There’s nothing faster, in any language - https://github.com/rust-lang/rust/pull/124032 . And sure, it’s possible that someone could write a C program that compares in speed to all the…
  42. …to work with just minified stack traces and not set up source maps to make them readable. [1]: https://github.com/rust-lang/rust/issues/99301
    comment by the_mitsuhiko · 2025-03-10 · in Stack Traces Are Underrated
  43. …code in Rust worse than C++ almost. A fully left-to-right syntax would be amazing. EDIT: found https://github.com/rust-lang/rust/issues/10011 and https://github.com/rust-lang/rfcs/pull/3577
    comment by dcsommer · 2025-03-08 · in Zig's dot star syntax (value.*)
  44. …out to an external assembler, I suppose. [1]: https://github.com/rust-lang/reference/pull/1689 [2]: https://github.com/rust-lang/rust/pull/134213
  45. Box::leak was added two years later in November 2017 https://github.com/rust-lang/rust/commit/360ce780fdae0dcb31c... >Crashes, stability, and performance issues are still not safety issues since there’s so many ways to cause those beyond…
    comment by milesrout · 2025-03-03 · in Effective Rust (2024)
  46. …perhaps because it requires a network transaction, it's very easy to introduce race conditions. [1] https://github.com/rust-lang/rust/issues/117485
    comment by Animats · 2025-03-02 · in Effective Rust (2024)
  47. The rust cygwin target has been merged (in a different attempt): https://github.com/rust-lang/rust/pull/134999
    comment by faho · 2025-02-27 · in Fish 4
  48. …There have been discussions about adding the target to Rust, but they have not been pursued: https://github.com/rust-lang/rust/issues/79854 https://github.com/rust-lang/rust/issues/5526
    comment by pbronez · 2025-02-27 · in Fish 4
  49. …Maybe it was Go? EDIT: Found it: 'rust-lang/rust#13871: "hello world" contains Lovecraft quotes' https://github.com/rust-lang/rust/issues/13871
    comment by runlevel1 · 2025-02-20 · in 1972 Unix V2 "Beta" Resurrected
  50. modules are meant to be the boundary for a safe abstraction, but sometimes you get fun holes like https://github.com/rust-lang/rust/issues/128872 where you can implement Copy for a type in a different module in the same crate, even if the…