Type checker quirk when rule incorrectly called as a function

[anderseknert]

package p

f := 1
r := f()

1 error occurred: policy.rego:5: rego_type_error: undefined function data.p.f

Which is correct, as f is not a function. Adding a default non-numeric value for f however makes the type checker somehow recognize f as one.

package p

default f := ""

f := 1
r := f()

I encountered this in a policy I reviewed.