aboutsummaryrefslogtreecommitdiff
path: root/docs/refman/loaderpickle.py
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2023-01-19 00:10:51 -0500
committerEli Schwartz <eschwartz@archlinux.org>2023-06-14 22:53:50 -0400
commitd558291abe9d851584e74f0154be819bc4baf207 (patch)
treede8eebae0071fe076bec2b40ffc56a988faa477c /docs/refman/loaderpickle.py
parentd87d912e5d2345f3c2f73fffb36820040cc997fe (diff)
downloadmeson-d558291abe9d851584e74f0154be819bc4baf207.zip
meson-d558291abe9d851584e74f0154be819bc4baf207.tar.gz
meson-d558291abe9d851584e74f0154be819bc4baf207.tar.bz2
add new FeatureBroken check class for annotating features that are really broken
This is useful for totally terrible stuff that we really dislike, but for some reason we are afraid to just use `mlog.deprecation()` and unconditionally tell people so. Apparently this is because it is totally absolutely vital that, when telling people something is so broken they should never ever ever use it no matter what, ever... we can't actually tell them that unless they bump the minimum version of Meson, because that's our standard way of introducing a **version number** to tell them when we first started warning about this. Sigh. We really want to warn people if they are doing totally broken stuff no matter what version of Meson they support, because it's not like fixing the thing that never worked is going to suddenly break old versions of meson. So. Here's some new functionality that always warns you, but also tells you when we started warning.
Diffstat (limited to 'docs/refman/loaderpickle.py')
0 files changed, 0 insertions, 0 deletions