Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support method parameters in @EnsuresNonnull{If} annotations #1099

Open
agrieve opened this issue Dec 18, 2024 · 4 comments
Open

Support method parameters in @EnsuresNonnull{If} annotations #1099

agrieve opened this issue Dec 18, 2024 · 4 comments

Comments

@agrieve
Copy link

agrieve commented Dec 18, 2024

Similar to bug #431

The checkerframework version of this annotation shows the syntax for this as:

   @EnsuresNonNullIf("#1")
   public boolean equals(@Nullable Object obj) { ... }

Not sure if it also supports just listing the parameter's name...

Here's an example in Chrome of where this would be useful:

    private void initializeDevices() {
        int[] deviceIds = mInputManager.getInputDeviceIds();
        for (int i = 0; i < deviceIds.length; i++) {
            InputDevice inputDevice = InputDevice.getDevice(deviceIds[i]);
            if (isGamepadDevice(inputDevice)) {
                // NullAway currently complains that inputDevice might be null.
                registerGamepad(inputDevice);
            }
        }
    }

    @EnsuresNonNullIf("#1") // Would love this to work!
    private static boolean isGamepadDevice(InputDevice inputDevice) {
        if (inputDevice == null) return false;

        if (Objects.equals(inputDevice.getName(), "uinput-fpc")) return false;

        return ((inputDevice.getSources() & InputDevice.SOURCE_JOYSTICK)
                == InputDevice.SOURCE_JOYSTICK);
    }
@msridhar
Copy link
Collaborator

Hi @agrieve I think you can do this with a @Contract annotation? https://github.com/uber/NullAway/wiki/Supported-Annotations#contracts Like for isGamepadDevice, you could write @Contract("null -> false") and I think it should work. For extra safety, I recommend passing -XepOpt:NullAway:CheckContracts=true to also verify the @Contract annotations are correct (we should really turn that on by default). Let us know if that would work for you. Also you can define your own annotation with simple name @Contract if you don't want to take a dependency on JetBrains annotations.

@msridhar
Copy link
Collaborator

Admittedly the current situation, with a mix of @Contract and @EnsuresNonNull{If} support, is a bit confusing. We could take as an action item supporting the method parameter syntax of @EnsuresNonNull{If} annotations, though at this point it would have to be low priority.

@agrieve
Copy link
Author

agrieve commented Dec 18, 2024

Ah, I thought that would be "check this returns false if the parameter is null", but not "returning false implies this is null". E.g. in my example it returns false even when the arg could be non-null.

@msridhar
Copy link
Collaborator

I always get confused by this stuff 🙂, but I think @Contract("null -> false") means if the parameter is null, the method definitely returns false. This is useful for NullAway since it implies that if the method returns true, the parameter cannot be null. So it should remove the false warning at the caller in your example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants