Skip to content

Problem: Existing interfaces with generic types may be only partially supportable with nullable types #275

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.

Sign up for GitHub

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

Jump to bottom
Open
natebosch opened this issue Mar 18, 2019 · 1 comment
Open

Problem: Existing interfaces with generic types may be only partially supportable with nullable types #275

natebosch opened this issue Mar 18, 2019 · 1 comment

Comments

@natebosch
Copy link
Member

Concrete example: List<int?>(1); is safe, but List<int>(1) will most likely need to throw at runtime because [null] is not a List<int> with NNBD. List<int>.filled(1, 0); would be safe.
@natebosch natebosch mentioned this issue Mar 18, 2019
Closed
@leafpetersen
Copy link
Member

Yes. The length setter is another known case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@natebosch @leafpetersen