Apparently, RangeSet is a @Beta API in Guava, and they stress that @Beta APIs should not be used in libraries.
I suggest we do something with that, otherwise, it results in a case where Calcite enforces all the consumers to depend on @Beta API which might disappear or drift. See https://github.com/google/guava/wiki/PhilosophyExplained#beta-apis It is literally the very first "important warning": https://github.com/google/guava#important-warnings 1, APIs marked with the @Beta annotation at the class or method level are subject to change. They can be modified in any way, or even removed, at any time. If your code is a library itself (i.e., it is used on the CLASSPATH of users outside your own control), you should not use beta APIs unless you repackage them. If your code is a library, we strongly recommend using the Guava Beta Checker to ensure that you do not use any @Beta APIs! Should we revert RangeSets? Should we ask Guava to promote it from @Beta? Vladimir
