Skip to content
This repository has been archived by the owner on May 7, 2023. It is now read-only.

Support columns with non-nullable data types #11

Closed
caseycrogers opened this issue May 6, 2021 · 3 comments
Closed

Support columns with non-nullable data types #11

caseycrogers opened this issue May 6, 2021 · 3 comments

Comments

@caseycrogers
Copy link
Collaborator

caseycrogers commented May 6, 2021

Currently all columns have nullable data types. If a user has data that explicitly should not be null, this makes their code more verbose (they have to add ! everywhere) and doesn't enforce non-null input.

To support non-nullable data types, we should add a non-nullable column and/or non-nullable DataFrame.

@synw
Copy link
Owner

synw commented May 9, 2021

Good idea. Should this be done before the next big release on pub with null safety? Should we publish or wait?

@caseycrogers
Copy link
Collaborator Author

caseycrogers commented May 10, 2021

I haven't thought too hard about how to implement this yet, but I think it's going to be a bit messy and painful. Currently, we're blocking anyone who wants to update their entire app to null safety-they can't update until df supports null safety. IMO we should publish ASAP to unblock people and then add a non-nullable DataFrame later.

@synw
Copy link
Owner

synw commented May 15, 2021

0.4.0-nullsafety.0 is published on pub

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

No branches or pull requests

2 participants