We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
i vote for nullable types like in ts, kotlin, dart. with '?' and '??' operator.
Sorry, something went wrong.
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 )
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: