Hi,
I suggest we add nullness verification to the main (non-test) code.
That would make the code easier to follow, and it would avoid NPEs.
checkerframework is an established verification framework for Java, and
they do ~monthly releases ( https://checkerframework.org/changelog.txt )
The
Vladimir Sitnikov created CALCITE-4286:
--
Summary: Remove NonNull annotations
Key: CALCITE-4286
URL: https://issues.apache.org/jira/browse/CALCITE-4286
Project: Calcite
Issue Type:
Vladimir Sitnikov created CALCITE-4285:
--
Summary: Replace jsr305 dependency with checkerframework and
errorprone_annotations
Key: CALCITE-4285
URL: https://issues.apache.org/jira/browse/CALCITE-4285
Vladimir Sitnikov created CALCITE-4284:
--
Summary: ImmutableBeans: make reference properties non-nullable by
default
Key: CALCITE-4284
URL: https://issues.apache.org/jira/browse/CALCITE-4284
Danny Chen created CALCITE-4283:
---
Summary: Promote the error message when creating table function
scan with non table functions
Key: CALCITE-4283
URL: https://issues.apache.org/jira/browse/CALCITE-4283
Danny Chen created CALCITE-4282:
---
Summary: Promote the window table functions window attribute data
type with precision 3
Key: CALCITE-4282
URL: https://issues.apache.org/jira/browse/CALCITE-4282