(🐞) An error should be reported when reveal_type is used but not called

[KotlinIsland]

reveal_type
not_defined

main.py:2:1: error: Name "not_defined" is not defined  [name-defined]
Found 1 error in 1 file (checked 1 source file)

Issue:

When reveal_type is called (reveal_type(1)) mypy reports a note and exits with status 1, but when reveal_type is used as a value without being called mypy doesn't report any error or note.

reveal_type

actual:

Success: no issues found in 1 source file

expected:

main.py:1:1: error: reveal_type must be called [misc]
Found 1 error in 1 file (checked 1 source file)

[hauntsaninja]

This is intentional and documented. mypy (and other type checkers) treat reveal_type like a builtin

[KotlinIsland]

@hauntsaninja Thanks for the quick response!, but I think you might have mis-understood my bug report. I'm well aware of how reveal_type works, this issue I'm reporting is that when reveal_type is called (reveal_type(1)) mypy reports a note and exits with status 1, but when reveal_type is used as a value without being called mypy doesn't report any error or note.

I've updated the OP to clarify.

[hauntsaninja]

Okay, I can see how a non-zero exit code would be nice to have there, but this is low priority for me.

On a similar note, maybe we shouldn't have non-zero exit status code for use of typing.reveal_type in 3.11 cc @JelleZijlstra

[JelleZijlstra]

I think the exit status issue is muddling the waters here. That's an unrelated change.

The original request was for an error if you use reveal_type without calling it. I guess we could do that but it doesn't seem worth the effort.

[KotlinIsland]

I think that exit 1 on typing.reveal_type is still good, it's completely useless and just gonna spam up the output of runs so mypy failing would be good to stop committing of code like that IMO.