Rustc-dev-guide Alternatives

rustc-dev-guide reviews and mentions

• The rust project has a burnout problem
  3 projects | news.ycombinator.com | 17 Jan 2024

  yes, it's possible! that list doesn't exist today but i would love to create it. i wrote a draft a few years ago before shifting to other work; someone recently expressed interest in reviving that project: https://github.com/rust-lang/rustc-dev-guide/pull/1463

  <3 i'm glad you enjoyed it

• How Rust transforms into Machine Code.
  5 projects | /r/rust | 3 Jun 2023

  It's possible - you could open an issue on the rustc-dev-guide repo if you'd like. https://github.com/rust-lang/rustc-dev-guide/

• Accessible Documentation?
  6 projects | /r/rust | 21 Nov 2022

  I'm very confident that this would be well received! I'm not sure where the source code for rustdoc lives, but I know that the internals getting started guide is here: https://github.com/rust-lang/rustc-dev-guide/blob/master/src/rustdoc.md. That would be a good place to start if you're looking into how the HTML is generated.

• Yet another command line argument parser: bpaf 0.5.5
  7 projects | /r/rust | 2 Sep 2022

  Do you have links to any good info about how much rustc reuses from previous runs? This is the first time i hear about reuse at the function level. I guess the rustc-dev-guide would be a good place for me to start?

• Discussion Thread
  1 project | /r/neoliberal | 27 Aug 2022

  Inspired by the rust compiler, you could represent the entire state of the application as a graph of operations with inputs and outputs. You can hash all the inputs and use that to memoize the operations, so that you don't have to repeat them, you can cache them in memory or on disk, and it helps you track which parts of the app state actually change between user operations and you can then be sure you put all the changes in the undo/redo stack, and so that you don't have to store duplicate copies of things that don't change. (How's that for a run-on sentence?) You could run a general binary diff algorithm between subsequent versions of the same operation with different inputs to try to reduce the memory used by storing the different versions, and have specialized diff algorithms for specific types of data. (How do you identify related operations? How much CPU does this use?) You can have a background task that compresses older versions with LZ4 or zstd. You can have a background task that saves older versions on-disk when there's memory pressure.

• What’s everyone working on this week (11/2022)?
  7 projects | /r/rust | 14 Mar 2022

  I contributed a couple small bugfixes for issues I ran into along the way as well. 1, 2

• Best practices for writing code comments
  1 project | news.ycombinator.com | 24 Dec 2021

  It's rustdoc: https://github.com/rust-lang/rustc-dev-guide/blob/master/src...

  > Rustdoc actually uses the rustc internals directly. It lives in-tree with the compiler and standard library. This chapter is about how it works. For information about Rustdoc's features and how to use them, see the Rustdoc book. For more details about how rustdoc works, see the "Rustdoc internals" chapter.

• A note from our sponsor - SaaSHub
  www.saashub.com | 3 Dec 2024

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