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

Strict Nil Checks #2

Open
avivcarmis opened this issue Aug 8, 2022 · 2 comments
Open

Strict Nil Checks #2

avivcarmis opened this issue Aug 8, 2022 · 2 comments

Comments

@avivcarmis
Copy link
Contributor

avivcarmis commented Aug 8, 2022

Do we want to go with the direction of Swift, Kotlin, and TypeScript with nullable types?

Or the direction of Rust and Scala with Option type?

More context in this blog post section.

@qrhfz
Copy link

qrhfz commented Jan 26, 2023

i vote for nullable types like in ts, kotlin, dart. with '?' and '??' operator.

@StephanSchmidt
Copy link

What fits best into Go IMHO would be a Zig approach.

!int for an error result (short for (int, error))
?int for a nullable result

( prefix modifiers like []int )

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

No branches or pull requests

3 participants