Hacker GitHub

← All repos

rust-lang/rust

View on GitHub ↗ ★ 121,092 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. …(and public) Default implementation for the struct. There was an issue on the tracker in the past ( https://github.com/rust-lang/rust/issues/42692 ) but the change is big enough that it would require an RFC, actual design and consensus,…
    comment by masklinn · 2018-08-17 · in What else is in Go 1.11?
  2. We did, eventually, after years, define it as a full byte though. https://github.com/rust-lang/rust/pull/46156
  3. …As for the rationale behind moving away from jemalloc as a default, the tracking issue is here: https://github.com/rust-lang/rust/issues/36963 (TL;DR: lower maintenance burden, easier cross-compilation, smaller binaries, better system…
    comment by kibwen · 2018-08-02 · in Announcing Rust 1.28
  4. …generate test functions using libtest. I'm not very familiar with the internals, but they're here: https://github.com/rust-lang/rust/blob/master/src/librustdoc...
    comment by djrenren · 2018-07-23 · in The internals of testing in Rust in 2018
  5. …Rust libraries, like libsyntax) without waiting for 30 minute builds after every minor change? [0]: https://github.com/rust-lang/rust/issues/36629 [1]: https://github.com/rust-lang/rfcs/issues/612
    comment by cornstalks · 2018-07-23 · in The internals of testing in Rust in 2018
  6. …which helps put this in further context. I think the original un-minimized crashing code was this: https://github.com/rust-lang/rust/issues/52213#issuecomment-... That's clearly more readable, and that's what more typical rust looks like.
    comment by TheDong · 2018-07-20 · in Announcing Rust 1.27.2
  7. …ub.com/rust-lang/rfcs/blob/master/text/1598-gene... and comments can be left on the tracking issue at https://github.com/rust-lang/rust/issues/44265 .
  8. https://github.com/rust-lang/rust/issues/11927 is the discussion when minimal OS X version for Rust was bumped to 10.7.
  9. …with a similar train of thought, this PR describes the standard sorting algorithm used in Rust: https://github.com/rust-lang/rust/pull/38192
  10. …restrict says “this does not alias”, which &Ts trivially do. It goes on &mut T. For example, see https://github.com/rust-lang/rust/pull/31545 , we had to remove this for a few releases due to an LLVM bug; it'll be back in the next release.…
    comment by steveklabnik · 2018-06-30 · in Rust pointers for C programmers
  11. …how it was handled. These arose because `restrict` is comparatively rarely used in C / C++ code. https://github.com/rust-lang/rust/issues/31681
  12. No. Rust has always had C-family syntax. You can look at the first public commit with the code at https://github.com/rust-lang/rust/tree/d6b7c96c3eb29b9244ece... ; src/test/run-pass shows lots of examples of the syntax.
    comment by chrismorgan · 2018-06-24 · in Rust 2018: an early preview
  13. …of the intents is to make it easier to audit for what is publicly exposed and what isn't. Found it: https://github.com/rust-lang/rust/issues/45521
    comment by epage · 2018-06-23 · in Rust 2018: an early preview
  14. …Stabilizing inline asm in its current form would be a mistake. It's simply not ready. [0]: https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Ais...
    comment by roblabla · 2018-06-22 · in Announcing Rust 1.27
  15. ▲ 5
    Rust:Initial PR for async/await syntax is open
    story by ngaut · 2018-06-16 · 0 comments
  16. …the default in gfortran. It looks like the equivalent option is still under discussion for rust: https://github.com/rust-lang/rust/issues/21690
    comment by ihnorton · 2018-06-07 · in Fortran is still a thing (2017)
  17. …https://www.ralfj.de/blog/2017/06/09/mutexguard-sync.html for an area where we were unsound, and https://github.com/rust-lang/rust/pull/45267#issuecomment-33... for an area where we were overly restrictive, and could remove some bounds…
    comment by steveklabnik · 2018-06-05 · in Announcing Rust 1.26.2
  18. We've experimented with MIR-only rlibs - https://github.com/rust-lang/rust/issues/38913#issuecomment-... has some recent data on it - which seem to me like the best approach for solving this, but it needs more work. Eventually, we might…
  19. s/z was made stable ten days ago: https://github.com/rust-lang/rust/pull/50265 So, two releases :)
  20. …support on top of that. Looks like gnzlbg put more effort into it, but ran into similar issues: https://github.com/rust-lang/rust/issues/42743#issuecomment-...
    comment by lambda · 2018-05-30 · in Mono on AIX and IBM i
  21. …fair comparison :) > "Containers should provide some way to not panic on failed allocations" https://github.com/rust-lang/rust/issues/29802 Definitely a problem, but it's not what people usually call "memory safety". The problem you…
  22. …stdlib OutOfMemory errors: "Containers should provide some way to not panic on failed allocations" https://github.com/rust-lang/rust/issues/29802
  23. https://github.com/rust-lang/rust/pull/50000 is the first bit, https://github.com/rust-lang/rust/issues/49879 is the tracking issue.
    comment by steveklabnik · 2018-05-29 · in When FFI Function Calls Beat Native C
  24. …and so &mut T can be optimized more aggressively. (We recently turned these optimizations back on: https://github.com/rust-lang/rust/pull/50744 )
    comment by steveklabnik · 2018-05-28 · in An embedded database written in Rust
  25. …For example, lots of people had to downgrade packages on MinGW recently for a bit before fixed, see https://github.com/rust-lang/rust/issues/47048
    comment by kodablah · 2018-05-26 · in Go Is a Shop-built Jig (2014)
  26. Both, it landed a few hours ago, and so will be in 1.28 stable. Here's the PR: https://github.com/rust-lang/rust/pull/50744
    comment by steveklabnik · 2018-05-19 · in On Competing with C Using Haskell (2017)
  27. std::str::from_bytes is that API. Rust’s current implementation of full validation: https://github.com/rust-lang/rust/blob/2a3f5367a23a769a068c3... I have a vague feeling there’s an even faster path for probably-ASCII out there, but I…
  28. …feature, so this footnote gives a false sense of optimism. Furthermore, as per the discussion at https://github.com/rust-lang/rust/issues/28979 , it's very unclear whether or not the stable form of this feature will end up using XID_start…
    comment by kibwen · 2018-05-16 · in Rust turns three
  29. …nonnull %2) #2, !dbg !26, !srcloc !27 Hmm… seems to be related to this Rust bug: https://github.com/rust-lang/rust/issues/16383
  30. …to land at approximately the same time. For example, coming up next in 1.27 is stable SIMD: https://github.com/rust-lang/rust/pull/49664 (though only for x86/x86_64 at first; more platforms and high-level crossplatform APIs are on the way).
    comment by kibwen · 2018-05-10 · in Rust 1.26 released
  31. …used most of those features in Rust, except for Address Sanitizer. But even ASan is available now: https://github.com/rust-lang/rust/pull/38699 I remember spending hours using Valgrind on Rust code back in 2011 to track down codegen…
    comment by pcwalton · 2018-05-01 · in How to speed up the Rust compiler in 2018
  32. …Rust certainly has the potential for exponential times when performing large inference. [1]: https://github.com/rust-lang/rust/issues/22204
    comment by shepmaster · 2018-04-30 · in How to speed up the Rust compiler in 2018
  33. …tracking ticket for the larger-scale reworking of the compiler internals for better performance: https://github.com/rust-lang/rust/issues/48547 I think there are a couple of major reasons why rustc is slow, and then a lot of ones which…
  34. If you're interested in the current "grand plans" for performance, check out this issue: https://github.com/rust-lang/rust/issues/48547 The query parallelization work has been coming along. Also it was recently discovered that building…
  35. …For example, here's where arielb1 discovered that the original scoped threads design was unsound: https://github.com/rust-lang/rust/issues/24292 (which sparked a large debate about whether mem::forget should be allowed in safe code:…
    comment by oconnor663 · 2018-04-30 · in How to speed up the Rust compiler in 2018
  36. …problems. It is relatively easy to create a situation where you overflow your program. See here: https://github.com/rust-lang/rust/issues/50049 Googling around, there are many situations where bad code can lead to an overflow and your code…
  37. Assuming nothing catastrophic happens in the next five days, https://github.com/rust-lang/rust/pull/49664 can be merged, by the way. So that'll be one thing off your list as of 1.27.
    comment by steveklabnik · 2018-04-12 · in A Gentle Introduction to Rust
  38. …a normal macro in that it doesn't expand to a bunch of Rust code. I found that pretty neat. [0] - https://github.com/rust-lang/rust/blob/master/src/libcore/ma... [1] - https://github.com/rust-lang/rust/blob/e8af0f4c1f121263e55da...
  39. …intrinsics) eats into many of the use cases for inline ASM. Not all of course, but many. :-) [1] - https://github.com/rust-lang/rust/issues/29722
    comment by burntsushi · 2018-03-29 · in Rust 1.25 released
  40. I know this won't help you, but there is an issue tracking this: https://github.com/rust-lang/rust/issues/43353
  41. The tracking issue for const generics is here: https://github.com/rust-lang/rust/issues/44580
    comment by kibwen · 2018-03-12 · in Rust's 2018 roadmap
  42. So, we almost made str a library type, but there were downsides and not a lot of upsides. https://github.com/rust-lang/rust/pull/19612 > no other data type does? You could argue that slices are a primitive type to arrays (also a primitive…
  43. ….parse() vs .into()), shipping 1.0 without async/await, and the whole mess with strings. 0: https://github.com/rust-lang/rust/issues?utf8=%E2%9C%93&q=is... 1: https://github.com/rust-lang/rfcs/issues?utf8=%E2%9C%93&q=is... 2:…
  44. …isn't a problem regardless: "There are only Copy types on the rust stack frame being jumped over." https://github.com/rust-lang/rust/issues/48251
    comment by mkj · 2018-03-02 · in Announcing Rust 1.24.1
  45. …it's isolated to clearly marked code (except for some minor bugs in Rust that will be fixed - see https://github.com/rust-lang/rust/issues?utf8=%E2%9C%93&q=is... ). Instead TypeScript has a bunch of serious unfixed design flaws that make…
  46. Though sadly casting float conversions are still UB. There's a really good writeup about it here: https://github.com/rust-lang/rust/issues/10184#issuecomment-...
    comment by andromeduck · 2018-02-19 · in The Evil Within the Comparison Functions
  47. Sure, and the code deals with that case. https://github.com/rust-lang/rust/blob/5cf55165fae5c8538db5c... This does mean you have some somewhat pathological cases, but they're relatively rare because most strings come from only a couple…
    comment by Manishearth · 2018-02-15 · in Rust 1.24
  48. https://github.com/rust-lang/rust/pull/46735 TL;DR, it's not a naive straight `memchr`. `memchr` will generate false positives, then they use knowledge of UTF-8 to weed out the false positives. The pathological case is worse, but the…
    comment by stouset · 2018-02-15 · in Rust 1.24
  49. Quoting a comment I made at https://github.com/rust-lang/rust/pull/27867#issuecomment-22... about that: One other potential issue with this (an issue that also applies to GNU make's MAKE_TERMOUT and MAKE_TERMERR environment variables,…
    comment by JoshTriplett · 2018-02-07 · in Disabling ANSI color output
  50. …as complex as Rust's compiler. Especially when there are many currently known bugs of this sort: https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Ais...