-
when building with cargo these env variables are injected for crates to use.
https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates
currentl…
-
In Rustc we have this code
````rust
macro_rules! late_lint_mod_passes {
($macro:path, $args:tt) => {
$macro!(
$args,
[
HardwiredLints: Hardwi…
-
This is a tracking issue for adding a Stable compiler driver that tools can use to extend the Rust compiler. This would replace the existing `rustc_smir::run!()` macro.
```[tasklist]
### Tasks
…
-
@ccbrown Just have a few questions so far that I haven't been able to figure out.
1 - How to pass children through for custom components? Maybe we need a `Fragment` component here?
```rust
#[de…
-
The libc crate has some macros, called `s!`, `f!`, etc. which take a series of items:
```rust
f! {
fn foo();
fn bar();
// ...
}
```
I know that formatting macros is very tricky…
-
### Code
MWE below, also tested on nightly (via the playground). Interestingly the error goes away if I manually inline the `Node::new` calls. Minimised from a filter graph that uses trait objects f…
-
So, what is preventing this?
It seems that we do have the source of truth from the Rust side. `nif`, `NifStruct`, and other Rustler macros have access to the typed raw arguments/fields; they just d…
-
[This page](https://crates.io/crates/static_assert_macro) links to https://nodakai.github.io/rust-static_assert_macro/static_assert_macro, which is a dead link.
-
# Behind the Scenes of Rust String Formatting: format_args!() - Mara's Blog
The fmt::Arguments type is one of my favorite types in the Rust standard library. It’s not particularly amazing, but …
-
To use multiple languages in a single Markdown file, It would be useful to move `block_name_prefix`, `macro_start` and etc. from `[parsr]` section in `Yarner.toml` file to language specific settings.…