> Are you willing to help with fixing the bits that you identified?
> Could you suggest timeframes when you can implement that?
I can’t tell whether you sincerely want my help. I’ll create a patch fixing the
three items. I’m fearful that you will take issue with what I put in the patch
and my time will be wasted.
> Julian>PolyNull is difficult to understand
>
> I agree PolyNull is not the most obvious thing, however, "arrays vs
> annotations" is even harder :)
> I think I can add a couple of words on PolyNull to develop/index.md.
I don’t think that’s the solution. Most people won’t read it, or remember it,
and we should not expect them too. I think PolyNull needs to be explained in
words each time it is used in a public method. I’m happy to do that.
> Julian>* Remove the changes to 2020-10-06-release-1.26.0.md
>
> Can you please clarify what is wrong with that change?
> Do you think Calcite 1.26 is a good release which people should use in
> production systems like 1.25 and other versions?
> Do you think people should prefer upgrading to 1.26 as soon as possible?
> Do you have better wording for the warning?
It doesn’t belong as part of this change.
When I challenged you about it last time you implied it was there by accident
(because you had recently rebased), and yet it’s still here.
> The added Wrapper.unwrapOrThrow is API.Status.INTERNAL. What is the problem
> with adding such a method?
Because you promised you would not.
Julian
