🌐 AI搜索 & 代理 主页
Skip to content

Conversation

@msridhar
Copy link
Collaborator

@msridhar msridhar commented Aug 7, 2025

Fixes #1238

Before we were missing a fallback case; now we just use the type of the expression computed by javac (to be improved in the future).

Summary by CodeRabbit

  • Bug Fixes

    • Improved handling of nullable type variables in generic methods to ensure correct type inference in assignment contexts.
  • Tests

    • Added a new test to verify correct behavior when assigning non-nullable arrays to nullable array parameters in generic methods.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 7, 2025

Walkthrough

A bug fix was made to the generic type inference logic for method calls in the NullAway static analysis tool, ensuring correct handling when the assignment context type is nullable and the type variable has a nullable upper bound. A new regression test was added to verify this fix for generic methods returning arrays.

Changes

Cohort / File(s) Change Summary
Generic type inference handling
nullaway/src/main/java/com/uber/nullaway/generics/GenericsChecks.java
Modified inferGenericMethodCallType to explicitly substitute the type variable with the original expression type (exprType) when the assignment context is nullable and the type variable has a nullable upper bound.
Regression test for generic method inference
nullaway/src/test/java/com/uber/nullaway/jspecify/GenericMethodTests.java
Added the issue1238 test to verify that a generic method with a nullable-bounded type variable correctly infers array types when assigned to a nullable array parameter.

Sequence Diagram(s)

sequenceDiagram
    participant Test as GenericMethodTests.issue1238()
    participant Mediator as CreatorMediator
    participant Bridge as WebFeedBridge

    Test->>Mediator: get(Key<byte[]>)
    Mediator-->>Test: byte[]
    Test->>Bridge: followFromId(byte[], ...)
    Bridge-->>Test: (no error)
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Assessment against linked issues

Objective Addressed Explanation
Fix crash when inferring generic return array type in assignment to nullable array parameter (#1238)
Add regression test to reproduce and verify fix for generic method with nullable type variable returning arrays (#1238)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes detected.

Note

🔌 MCP (Model Context Protocol) integration is now available in Early Access!

Pro users can now connect to remote MCP servers under the Integrations page to get reviews and chat conversations that understand additional development context.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 92c9304 and a7a696a.

📒 Files selected for processing (2)
  • nullaway/src/main/java/com/uber/nullaway/generics/GenericsChecks.java (1 hunks)
  • nullaway/src/test/java/com/uber/nullaway/jspecify/GenericMethodTests.java (1 hunks)
🔇 Additional comments (2)
nullaway/src/main/java/com/uber/nullaway/generics/GenericsChecks.java (1)

517-521: LGTM! Excellent fix for the generic method call inference issue.

This fallback case correctly handles the scenario where both the assignment context type is nullable and the type variable has a nullable upper bound. By explicitly mapping the type variable to the original expression type (exprType), this prevents the ClassCastException described in issue #1238 where a TypeVar was incorrectly cast to an ArrayType. The fix ensures there's always a proper substitution in the map rather than leaving it undefined.

nullaway/src/test/java/com/uber/nullaway/jspecify/GenericMethodTests.java (1)

741-776: Excellent regression test for issue #1238.

This test comprehensively covers the bug scenario from the Chromium codebase:

  1. Generic method with nullable upper bound: <T extends @Nullable Object> T get(Key<T> key)
  2. Array type compatibility: byte[] (from Key<byte[]>) being passed to a parameter expecting byte @Nullable []
  3. Assignment context inference: The fix ensures proper type substitution when the generic method return type is a type variable with nullable upper bound

The test validates that the type inference correctly handles this case without crashing and allows the valid assignment. This directly validates the fix in GenericsChecks.java.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch issue-1238

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@msridhar msridhar requested a review from yuxincs August 7, 2025 22:41
@msridhar msridhar merged commit 7b64688 into master Aug 8, 2025
11 checks passed
@msridhar msridhar deleted the issue-1238 branch August 8, 2025 02:46
haewiful pushed a commit to haewiful/NullAway01 that referenced this pull request Aug 9, 2025
Fixes uber#1238 

Before we were missing a fallback case; now we just use the type of the
expression computed by `javac` (to be improved in the future).

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Bug Fixes**
* Improved handling of nullable type variables in generic methods to
ensure correct type inference in assignment contexts.

* **Tests**
* Added a new test to verify correct behavior when assigning
non-nullable arrays to nullable array parameters in generic methods.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
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

Successfully merging this pull request may close these issues.

Crash wrt inferring generic return array type

3 participants