undefined | Better HN

0 pointsocamoss24d ago0 comments

It's acknowledged at the end of the "infer any" strategy, but perhaps worded poorly.

> To improve type safety in these situations, type checkers that infer Any for empty containers can choose to generate extra type errors that warn the user about the insertion of an Any type. While this can reduce false negatives, it burdens developers by forcing them to explicitly annotate every empty container in order to silence the warnings.

ie: "type checkers that don't infer container types can emit an error and require users to annotate"

0 comments

maleldil23d ago

I missed that. At least pyright will only emit an error if `typeCheckingMode` is strict (which forbids `Unknown`). It will happily treat `Unknown` as `Any` in basic mode.

j / k navigate · click thread line to collapse

0 pointsocamoss24d ago0 comments

It's acknowledged at the end of the "infer any" strategy, but perhaps worded poorly.

ie: "type checkers that don't infer container types can emit an error and require users to annotate"

0 comments

maleldil23d ago

I missed that. At least pyright will only emit an error if `typeCheckingMode` is strict (which forbids `Unknown`). It will happily treat `Unknown` as `Any` in basic mode.

j / k navigate · click thread line to collapse