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
AllStoriesComments NewestTopOldest
  1. …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
  2. …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)
  3. …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
  4. 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…
    comment by eddyb · 2018-06-05 · in How to speed up the Rust compiler some more in 2018
  5. s/z was made stable ten days ago: https://github.com/rust-lang/rust/pull/50265 So, two releases :)
    comment by steveklabnik · 2018-05-31 · in Actix: a small, pragmatic, and fast Rust web framework
  6. …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
  7. …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…
    comment by Yoric · 2018-05-30 · in Zig: programming language designed for robustness optimality and clarity [video]
  8. …stdlib OutOfMemory errors: "Containers should provide some way to not panic on failed allocations" https://github.com/rust-lang/rust/issues/29802
    comment by espeed · 2018-05-30 · in Zig: programming language designed for robustness optimality and clarity [video]
  9. 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
  10. …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
  11. …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)
  12. 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)
  13. 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…
    comment by chrismorgan · 2018-05-16 · in Validating UTF-8 strings using as little as 0.7 cycles per byte
  14. …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
  15. …nonnull %2) #2, !dbg !26, !srcloc !27 Hmm… seems to be related to this Rust bug: https://github.com/rust-lang/rust/issues/16383
    comment by comex · 2018-05-14 · in How Rust 1.26 more than tripled the speed of my code
  16. …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
  17. …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
  18. …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
  19. …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…
    comment by lambda · 2018-04-30 · in How to speed up the Rust compiler in 2018
  20. 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…
    comment by mastax · 2018-04-30 · in How to speed up the Rust compiler in 2018
  21. …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
  22. …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…
    comment by csomar · 2018-04-27 · in Reflections on Rust, and the Sand Castle Metaphor
  23. 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
  24. …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...
    comment by phyllostachys · 2018-04-05 · in Making a Statically-Linked, Single-File Web App with React and Rust
  25. …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
  26. I know this won't help you, but there is an issue tracking this: https://github.com/rust-lang/rust/issues/43353
    comment by saghm · 2018-03-24 · in 100 days with Rust: a series of brick walls
  27. 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
  28. 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…
    comment by steveklabnik · 2018-03-08 · in Rust needs to run, and be easy to use, on every platform
  29. ….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:…
    comment by ComputerGuru · 2018-03-08 · in Rust needs to run, and be easy to use, on every platform
  30. …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
  31. …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…
    comment by devit · 2018-02-19 · in Maybe you don't need Rust and WASM to speed up your JS
  32. 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
  33. 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
  34. 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
  35. 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
  36. …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...
    comment by gpm · 2018-02-04 · in RustBelt: securing the foundations of the Rust programming language
  37. …not correctly handling certain cases. Is it really that trivial? When looking through https://github.com/rust-lang/rust/blob/master/src/librustc_b... , it is not at all clear that these rules cover everything to me. There are some complex…
    comment by bennofs · 2018-02-04 · in RustBelt: securing the foundations of the Rust programming language
  38. …borrowck rules are sufficient to catch all possible mistakes? For example, does it catch stuff like https://github.com/rust-lang/rust/issues/31287 or https://github.com/rust-lang/rust/issues/38899 ?
    comment by bennofs · 2018-02-04 · in RustBelt: securing the foundations of the Rust programming language
  39. …library, demonstrating that our model of Rust is realistic enough to be useful. The bug was https://github.com/rust-lang/rust/issues/41622 .
    comment by chrismorgan · 2018-02-04 · in RustBelt: securing the foundations of the Rust programming language
  40. …"myriad of features" with each release, and most of those it adds are library stuff, see for 1.23: https://github.com/rust-lang/rust/blob/master/RELEASES.md#ve... And with respect to non-library features currently in-flight, by and large…
    comment by masklinn · 2018-01-31 · in C++ and the Culture of Complexity (2013)
  41. …after all, the very logic that gave us Rust.) [1]: https://github.com/rust-lang/rfcs/pull/1909 [2]: https://github.com/rust-lang/rust/issues/18806
    comment by deathanatos · 2018-01-25 · in Unsafe Zig Is Safer Than Unsafe Rust
  42. …on the topic, but it seems ([0]) that adding `#[no_mangle]` before `panic_fmt` should fix it. [0] https://github.com/rust-lang/rust/issues/38281
    comment by red75prime · 2018-01-14 · in Rust in 2018: easier to use
  43. …and stack cookies), which means that theoretically you could enable this for C and C++ as well. See https://github.com/rust-lang/rust/issues/16012
    comment by kibwen · 2018-01-11 · in Spectre and the end of langsec
  44. …implicitly link the stdlib by default, and the stdlib publicly exports the items in the prelude ( https://github.com/rust-lang/rust/blob/master/src/libstd/pre... ). So in the future when macros are namespaced just like every other item…
    comment by kibwen · 2018-01-08 · in Go’s hidden pragmas
  45. …behavior that is triggered by code outside of unsafe blocks, depending on how a result is used: https://github.com/rust-lang/rust/issues/33813 This basically exposes LLVM's poison semantics (a kind of deferred UB) to Rust code:…
    comment by cwzwarich · 2017-12-24 · in Undefined vs. Unsafe in Rust
  46. …to about 5 total languages. [1] https://marketplace.visualstudio.com/items?itemName=webfreak... [2] https://github.com/rust-lang/rust/issues/45218
    comment by mikebenfield · 2017-12-21 · in Rust in 2017: what we achieved
  47. I've filed a bug to elaborate, thanks! https://github.com/rust-lang/rust/issues/46879
    comment by steveklabnik · 2017-12-20 · in Rust vector guarantees
  48. That memory stuff isn't even part of Rust's runtime; it's compile time stuff. Here's Rust's runtime: https://github.com/rust-lang/rust/blob/master/src/libstd/rt....
    comment by steveklabnik · 2017-12-12 · in Re: Moving from PHP to Go and Back Again
  49. …implements this too. Being in std is a high bar. Beyond that, there are a host of other reasons: https://github.com/rust-lang/rust/commit/454882dcb7fdb03867d...
    comment by steveklabnik · 2017-12-06 · in Why I love Go
  50. Agree. Moreover, Rust compiler contains some dark areas which nobody wants to deal with. See https://github.com/rust-lang/rust/issues/38528 for example. Basically it means that Rust compiler can suddenly take exponential time and space for…
    comment by MageSlayer · 2017-12-04 · in Integrating “safe” languages into OpenBSD?