forked from loic-sharma/BaGet
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Enable nullability #96
Comments
I am pro on this. Because I personally like nullability very much, guarding us of |
This issue is stale because it has been open for 90 days with no activity. Remove the stale label, comment, or this will be closed in 5 days. |
This issue was closed because it has been stale for 5 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Enabling nullability will make it easier to not accidentally pass something potentially uninitialized and also simpler to see at what point we don't have to null-check everything.
I guess immediately enabling it globally would make a mess so maybe start with enabling it in
BaGetter.Protocol
and putting question marks where needed, thenBaGetter.Core
, then look how far that branch goes without getting tired.Just make a commit per project converted so we can merge early in order to minimize interference.
The text was updated successfully, but these errors were encountered: