LearnLib / automatalib / 12812848752

93%

Build Type

push

github

Committed by mtf90

Commit Message

cleanup {Static,Dynamic}{State,Node}Mappings

Accessing potential null-values is an inherent data-flow problem. By annotating the result type as @Nullable, we force all consumers to check for null, even in those cases where previous dataflow ensures non-nullability. The alternative would be to additionally track which items have been set and throw an IllegalArgumentException when not able to return a non-null value. However, since this will cause an exception as well, we might as well just let the code crash with a NullPointerException. Yes, it is not fail-fast, but the noise and overhead introduced by explicitly checking nullability does not justify the gains.

Run Details

54 of 55 new or added lines in 19 files covered. (98.18%)

1 existing line in 1 file now uncovered.

16559 of 18009 relevant lines covered (91.95%)

1.7 hits per line