-
[ES.30: Don’t use macros for program text manipulation](http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#a-nameres-macrosaes30-dont-use-macros-for-program-text-manipulation) states that mac…
-
### Describe the bug
Custom strategies are supported in dbt-core and allow users to write macros that define incremental merge startegies ( https://docs.getdbt.com/docs/build/incremental-strategy#c…
-
## minimized code
```Scala
type Opt[A] = A | Null
object Opt {
given ops as AnyRef {
inline def [A, B](inline lhs: Opt[A]) map (inline rhs: A => B): Opt[B] = ${ mapMacro('lhs, 'rhs) }
…
-
The "bottom" element of a Lattice is the identity element of the "join" operation.
The "top" element of a Lattice is the identity element of the "meet" operation.
But when using the `#[derive(Disj…
-
we have line! and column! macros. we can technically take out a pice of code with some context around it where assertion failed and add it to the error message
e.g.
```
Assertion Failure!
43 |…
-
I came across https://github.com/google/zerocopy/issues/388#issuecomment-1737817682 by chance. The same applies to this crate:
```rust
type S = &'static str;
#[derive(Copy, Clone, Debug, AnyBit…
-
It would be great if the assertion macros were to support specifying an error message with format parameters as the standard library assertions do.
Example:
```rust
assert_eq!(1, 2, "Numbers in t…
-
This can be really helpful when documenting what a particular assertion is
testing, and when an assertion fails at a later date it helps the person running
the test understand what went wrong, even if…
-
Blocked by #6
The builtin assertions are lackluster for testing in that they only cover `assert_eq`, `assert_ne`, `assert`, and `assert_match` (nightly). Ideally we should have the full collection…
-
When most assertion macros are called, they call another macro, and in the process expand the arguments originally passed to the assertion. Since stringification happens in `munit_assert_type_full`, a…