Could assert2 have a const_assert and a const_debug_assert?

[U007D]

Wondering if you'd be open to this as a part of assert2?

This would eliminate a dependency for me in many of my projects and presumably would for others too.

[de-vri-es]

Hey, it's certainly interesting, and providing a one-shop-stop for testing utilities is certainly something I would like for this crate.

The only problem I see is that we can't really do pretty assertions at compile time. I'm not aware of a way for proc macros to evaluate const expressions at compile time, so we cant do our own error formatting.

Another thing we should keep in mind is that assert2 comes with some dependencies that you probably don't want for normal builds. Currently, that is fine, because assert2 can be a dev-dependency. But you use it for const_assert it would have to be a regular dependency.

None of this is necessarily blocking (especially not the second one), it's just an explanation of why I haven't done it yet.

[U007D]

Good points re: pretty-printing.

Out of curiosity, why would a const_assert capability prevent assert2 from being usable as a dev dependency?

[de-vri-es]

assert2 could still be used as a dev-dependency, but const_assert itself could not, as it is always required during compilation.