When is a slice of any not a slice of any?
1–6 of 6 posts
Re: When is a slice of any not a slice of any?
#2Was expecting food taxonomy: when is a slice of food not a slice of food?
(Not go-lang.)
See cube rule of food identification for actual discussions on food taxonomy.
Re: When is a slice of any not a slice of any?
#3No post body was provided.
Re: When is a slice of any not a slice of any?
#4nonmeasurable sets
Re: When is a slice of any not a slice of any?
#5The first example used this signature:
func one[S []E, E any](s S)
func one[E any](s []E)
Re: When is a slice of any not a slice of any?
#6[]any isn't "any slice", but rather "a slice of some type, and that type could be anything."
It's not just a detail of the underlying runtime; there are very real, semantic problems that would occur if two(s) compiled. Consider what would happen if instead of just returning its input, two([]any) modified it:
func two(s []any) {
s[0] = "hello"
}
someInts := []int{1, 2, 3}
two(someInts) // this won't compile