Book-reader

My immediate thought would be to disallow it and either add a `d` suffix to be consistent with allowing `3f`, or just require a `.0`.

so something along the lines of `--validation=lenient` for no unused warnings, `--validation=strict` for unused warnings, and `--validation=obnoxious` for unused errors? or did you mean something like a `--unused` flag with...

It does, sorry for taking so long to check

this could be useful in some incredibly niche cases for creating a custom switch construct. for example with my tagged union library: ```cpp tu::@match(my_tagged_union, FOO, macro (val) { io::printfn("was FOO...

another use for anonymous macros is to define a constant using some level of conditions without needing to create a separate macro for it: ```cpp const Foo[] FOO = macro...

> Only asm("....") was intended to be available for these sections as in `asm{}` blocks weren't intended to be allowed in `@naked` functions?

oh, do you mean that `@naked` functions were intended to only be used with `asm` blocks and not regular code (even the `unreachable()` would be disallowed)?

running the example I gave at `-O1` and above now causes a compiler segfault

it doesn't allow the `unreachable()` due to it using parameters under `-O2`, but other than that I can't get it to crash anymore, so I'll close this and #1959. Thank...

valgrind logs because I was on my phone when I wrote this: ```cpp ==183562== Thread 5: ==183562== Conditional jump or move depends on uninitialised value(s) ==183562== at 0x152002F: std::__detail::__variant::__gen_vtable_impl::__visit_invoke(llvm::DwarfCompileUnit::constructVariableDIE(llvm::DbgVariable&, bool)::$_0&&,...