[
https://issues.apache.org/jira/browse/CALCITE-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18036319#comment-18036319
]
Julian Hyde commented on CALCITE-4099:
--------------------------------------
I’d say go for it. It will probably be hard work, but it will be useful work.
Remember that the test suite is the key asset here. (Especially in the age of
AI-driven coding, where if you have a good test suite the AI can write the
code.)
Approach this as an experiment. Start refactoring, and listen to what the test
suite is telling you. If you notice blind spots in the test suite, pause you
work, improve the test suite, and then resume or restart the refactoring.
Don’t worry too much about backwards compatibility. If you end up with a
simpler and more powerful way to represent null behavior (and maybe even
effects… see conversations in other cases this week) then it’s worth it, and
people can easily manually update their code.
> Unify Strong.Policy and NullPolicy
> ----------------------------------
>
> Key: CALCITE-4099
> URL: https://issues.apache.org/jira/browse/CALCITE-4099
> Project: Calcite
> Issue Type: Task
> Components: core
> Reporter: Ruben Q L
> Priority: Minor
>
> (discussion about this ticket started in CALCITE-4094)
> {{Strong.Policy}} and {{NullPolicy}} are two different enum that represent
> grosso-modo the same thing. The former is mostly used on the simplifier, and
> the latter on the code generation.
> To be studied if we could unify both entities and make it available through
> the SqlOperator.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
