> On Mar 19, 2024, at 2:43 PM, Daniel Lepage <dplep...@gmail.com> wrote:
>
> I'm not proposing that *any* value be made nillable, I'm proposing the
> explicit syntax
>
> var x uint8 | nil
>
> that would create a nillable uint8. A variable of type `byte` would still
> only take up one byte; a variable of type `byte | nil` would be larger.
> Existing code, which obviously doesn't use the `| nil` syntax because it
> doesn't exist yet, would be completely unaffected by this change.
Focusing the proposal like that was helpful, at least for me. The original
proposal? tldr;
Question: Assuming the following was currently possible with type constraints,
how would your proposal differ from the following?
type NillableUInt8 interface {
uint8 | nil
}
var x NillableUInt8
Also, if the above were possible in future Go, would that achieve the same
objectives you are seeking, or not? And if not, why not?
Finally, for the Go team, if that would be meet his objectives, would extending
type constraints in this manner be a viable potential?
-Mike
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/3CC3FD1B-D591-4B21-AE7B-0D9E5C821F31%40newclarity.net.
