-
This is a tracking issue for making `proc_macro` usable in all crates, not just those with crate type `proc-macro`. Advantages:
- Simplified testing of procedural macros
- Examples in the [API docs](…
-
**Is your feature request related to a problem? Please describe.**
Currently, SQL query strings can not be auto-formatted.
**Describe the solution you'd like**
Add an auto-format command to the C…
-
It is important that we deal with macros that declares types, because we should (at least have the option to) reflect these types in the Haskell bindings. For example, given
```
#define __S16_TYPE…
-
Let's support custom test macro, instead only `#[test]`. For instance, [here](https://github.com/h1alexbel/fakehub/issues/157) we need to use `#[tokio:test]`. Let's get rid of hardcoded `#[test]` insi…
-
Our macro "model" isn't perfect at handling what macros can actually do, notably we do not parse or handle "None" delimited groups today (https://github.com/rust-lang/rust/issues/67062, notably rustc …
-
Alright, this is a proposition that I don't know if it's possible with the current state of macros in Dart. This is based on my experience using the rust_core package, specially talking about early re…
-
Let's say you have two crates
* Crate A and Crate B
* Crate A imports crate B, and re-exports its modules
In crate B you have something like
```
//! crate B : lib.rs
pub mod whatever…
-
ashlang should support macro functions that return `static` values. Potential functions:
`dimensions!(v)` - returns the number of dimensions of `v` (0 for scalar)
`len!(v)` - returns the length of…
-
### Description
- OL is still using the old macro placer (macro_placement) rather than the new one (rtl_macro_placer). The old one should be considered deprecated and will eventually be removed fro…
-
#### Bug description
GoogleTest requires test suite names and test names used in the TEST macro not contain underscores (see https://google.github.io/googletest/faq.html).
Every file containing tes…