Changes for version 0.030

  • Feature
    • Thwarting modules that import compile-time warnings was a bad idea. Source filters are bad, full stop. Also, I didn't properly understand how warnings were being turned back on; there's a simpler way of avoiding e.g. experimental warnings being turned back on, which has now been documented.


an insistent alias for warnings::everywhere
an alias for warnings::everywhere
a way of ensuring consistent global warning settings