114: "operation already in progress",
	115: "operation now in progress",
	116: "stale NFS file handle",
	117: "structure needs cleaning",
	118: "not a XENIX named type file",
	119: "no XENIX semaphores available",
	120: "is a named type file",
	121: "remote I/O error",
	122: "disk quota exceeded",
	123: "no medium found",
	124: "wrong medium type",
	125: "operation canceled",

If an element of the iterable implements `link:{javadocPath}/org/gradle/api/Named.html[Named]`, then the name is used as property name.
The ordering of the elements in the iterable is crucial for reliable up-to-date checks and caching if not all of the elements implement `link:{javadocPath}/org/gradle/api/Named.html[Named]`.
Multiple elements which have the same name are not allowed.

	133:  "transport endpoint is already connected",
	134:  "transport endpoint is not connected",
	135:  "structure needs cleaning",
	137:  "not a XENIX named type file",
	138:  "no XENIX semaphores available",
	139:  "is a named type file",
	140:  "remote I/O error",
	141:  "unknown error 141",
	142:  "unknown error 142",
	143:  "cannot send after transport endpoint shutdown",

	133:  "transport endpoint is already connected",
	134:  "transport endpoint is not connected",
	135:  "structure needs cleaning",
	137:  "not a XENIX named type file",
	138:  "no XENIX semaphores available",
	139:  "is a named type file",
	140:  "remote I/O error",
	141:  "unknown error 141",
	142:  "unknown error 142",
	143:  "cannot send after transport endpoint shutdown",

	133:  "transport endpoint is already connected",
	134:  "transport endpoint is not connected",
	135:  "structure needs cleaning",
	137:  "not a XENIX named type file",
	138:  "no XENIX semaphores available",
	139:  "is a named type file",
	140:  "remote I/O error",
	141:  "unknown error 141",
	142:  "unknown error 142",
	143:  "cannot send after transport endpoint shutdown",

	133:  "transport endpoint is already connected",
	134:  "transport endpoint is not connected",
	135:  "structure needs cleaning",
	137:  "not a XENIX named type file",
	138:  "no XENIX semaphores available",
	139:  "is a named type file",
	140:  "remote I/O error",
	141:  "unknown error 141",
	142:  "unknown error 142",
	143:  "cannot send after transport endpoint shutdown",

	114: "operation already in progress",
	115: "operation now in progress",
	116: "stale file handle",
	117: "structure needs cleaning",
	118: "not a XENIX named type file",
	119: "no XENIX semaphores available",
	120: "is a named type file",
	121: "remote I/O error",
	122: "disk quota exceeded",
	123: "no medium found",
	124: "wrong medium type",
	125: "operation canceled",

	114: "operation already in progress",
	115: "operation now in progress",
	116: "stale file handle",
	117: "structure needs cleaning",
	118: "not a XENIX named type file",
	119: "no XENIX semaphores available",
	120: "is a named type file",
	121: "remote I/O error",
	122: "disk quota exceeded",
	123: "no medium found",
	124: "wrong medium type",
	125: "operation canceled",

	*Embed0a
	*Embed0b `json:"e,omitempty"` // treated as named
	Embed0c  `json:"-"`           // ignored
	Loop
	Embed0p // has Point with X, Y, used
	Embed0q // has Point with Z, used
	embed   // contains exported field
}

type Embed0 struct {
	Level1a int // overridden by Embed0a's Level1a with json tag
	Level1b int // used because Embed0a's Level1b is renamed
	Level1c int // used because Embed0a's Level1c is ignored

	// will fulfill this Template, but have a unique identity from the rest
	// of the StatefulSet. Each pod will be named with the format
	// <statefulsetname>-<podindex>. For example, a pod in a StatefulSet named
	// "web" with index number "3" would be named "web-3".
	// The only allowed template.spec.restartPolicy value is "Always".
	Template v1.PodTemplateSpec `json:"template" protobuf:"bytes,3,opt,name=template"`