RaytracingWeekend-CPP
quote
| RaytracingWeekend-CPP | quote | |
|---|---|---|
| 3 | 3 | |
| 12 | 1,226 | |
| - | - | |
| 5.6 | 7.3 | |
| about 1 month ago | 14 days ago | |
| C++ | Rust | |
| Creative Commons Zero v1.0 Universal | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
RaytracingWeekend-CPP
- C++ vs. Rust Build Times
-
Modules in the big three compilers: a small experiment
For example https://github.com/pjmlp/RaytracingWeekend-CPP.
-
Things I hate about Rust, redux
The same way as a crate file contains everything.
https://github.com/pjmlp/RaytracingWeekend-CPP/blob/main/One...
quote
-
C++ vs. Rust Build Times
A surprising source of slow compile times can be declarative macros in Rust [0].
I believe the core of the problem is that it has to reparse the code to pattern match for the macro.
One egregious patter is tt-munchers [1] where your macro is implemented recursively, requiring it to reparse the source on each call [2].
In one of my projects, someone decided to wrap a lot of core functions in simple macros (ie nt tt-munchers) to simplify the signatures. Unlike most macros which are used occasionally and have small inputs, this was a lot of input. When I refactored the code, I suspect dropping the macros is the reason CI times were cut in half and a clean `cargo check` went from 3s to 0.5s.
[0]: https://nnethercote.github.io/2022/04/12/how-to-speed-up-the...
[1]: https://veykril.github.io/tlborm/decl-macros/patterns/tt-mun...
[2]: https://github.com/dtolnay/quote/blob/31c3be473d0457e29c4f47...
-
Is generating code from JSON a good macro use case?
In the build.rs, call your code generation function (probably in a separate crate added in build-dependencies). This function will read your input files, and use something like quote to generate code.
-
Any good resources for learning Rust macros?
Or you can pair them with crates like syn, and quote for quasi-quoting, and then it's easy to make transformations on the AST of Rust input code. A lot of libraries do this for code-generation and hiding away a lot of complexity (example wasm-bindgen).
What are some alternatives?
v-mode - 🌻 An Emacs major mode for the V programming language.
cargo-expand - Subcommand to show result of macro expansion
hylo - The Hylo programming language
proc-macro-workshop - Learn to write Rust procedural macros  [Rust Latam conference, Montevideo Uruguay, March 2019]
cpp-vs-rust
Bytecode - A Rust proc-macro crate which derives functions to compile and parse back enums and structs to and from a bytecode representation
component-keycloak - Commodore Component for Keycloak
darling - A Rust proc-macro attribute parser
hickory - Command line tool for scheduling Python scripts
syn - Parser for Rust source code
rust-fsm - Finite state machine framework for Rust with readable specifications
todo_by - Compile-time lifetimes for comments.