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

Unbound generic copyWith (or even nullable bound) does not respect type nullability #253

Open
dzsonni opened this issue Jan 6, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@dzsonni
Copy link

dzsonni commented Jan 6, 2025

Nullability causes class to generate non-nullable copyWith function, basically preventing the copy from ever setting it to null.

classs Foo<T extends Object?> with FooMappable<T>{
    const Foo(this.value);
    
    final T value;
}
final Foo<String?> foo = Foo('foo');

foo.copyWith(null);

The value of foo after the copyWith will still be 'foo'.

@schultek schultek added the bug Something isn't working label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants