maint/check_docs_features should be made into a warning, pending significant improvement
I've just had another CI failure for maint/check_doc_features
. Sadly, I think the current situation is not tenable.
- I don't know what the rules are. (When and where to put what
docsrs
attribute.) - Really, this ought not to be necessary at all - it's just a complex human-edited bodge to work around tooling problems
- When the thing fails, it is not clear how to fix it
- When the thing fails, it is not even clear where the problem is (file and line number)
The benefit we get from this arrangement is that our autogenerated Rust API documentation has correct feature annotations. But the cost is that many MRs get blocked on hard to understand and hard to fix CI failures. This has started happening an awful lot now because we are working on the PT/bridge features, and those are all behind features.
In practice we have sometimes been working around this situation by adding the failures to the exception list.
I don't think this is a good tradeoff, in terms of the effort we are spending for the positive outcome.
Sorry, @trinity-1686a. I know you've been working hard to help us with CI issues, including this one.