20541, "lydia-duncan", "How to handle unstable warnings triggered in the provided modules?", "2022-08-29T17:59:30Z"
Users should not be troubled by things that are outside their control, and an unstable warning for a use of an unstable symbol in our library code (e.g. if the IO module uses an unstable symbol from the Range module or something) is something they don't have control over. However, since unstable symbols don't have an obvious replacement, it is not as easy for a developer to remove such uses. It seems fraught to merely ignore such warnings, but perhaps it is okay since developers will be able to perform updates when the unstable symbol is converted to its final form. Something needs to be done in the meanwhile, the question is: what should be done?
I currently favor:
- turning it off with
--warn-unstable - and adding a new flag to ensure we still see those messages, e.g.
--warn-unstable-develor something - and adding a job to test the test suite with that flag nightly
Other ideas?