proposal: constraints: rename package to "of"

[panyox]

snippet code

func Abs[V of.Number](v V) V{...}

func Sum[K comparable, V of.Number](m map[K]V) V {...}

it is simple and smooth to type the word "of" better then "constraints"

[davecheney]

There seems to be a pattern; the strings package contains symbols that relate to strings, the bytes package contains symbols that relate to slices of bytes, so the of package contains symbols related to, uh, prepositions?

But seriously, if you think it reads better, you can rename the import thusly

import of “constraints”

[robpike]

Too bad any is taken because any.Integer or any.Comparable reads nicely.

[fzipp]

My suggestion was is, because it contains the essence of types (lat. esse = to be): is.Integer, is.Comparable, is.Ordered.

[robpike]

Bikeshed entry number 4:some: some.Integer.

I do agree with the implication of the original comment that 'constraints' feels cumbersome.

[zephyrtronium]

The name of the package was brought up (as @fzipp mentioned) in discussion, and @rsc marked it as resolved. I agree "constraints" is quite long, but I don't see what's changed.

[panyox]

definitely agree, "constraints" is cumbersome, hope the go team make some change in the future

[zigo101]

Is it a good idea to make them all pre-declared?

[ianlancetaylor]

Is it a good idea to make them all pre-declared?

Not in my opinion. It's possible to write these in the language (which is a good thing), so there is no reason to predeclare them.

[earthboundkid]

My vote at the time of the discussion was types, but sadly, it seems the 🚢 has sailed.

[cristaloleg]

anyof ? 👀 anyof.Number, anyof.Ordered.

[Warmbellycat]

import isA “constraints”

isA.Number
isA.Ordered

[zhuah]

how about std? i like this, short, means standard but not builtin.
like cpp and rust, they also has a std namespace or crate.