} else {
					msg = "missing type parameter name"
					// go.dev/issue/60812
					if len(list) == 1 {
						msg += " or invalid array length"
					}
				}
			} else {
				msg = "mixed named and unnamed parameters"
			}
			p.syntaxErrorAt(errPos, msg)
		}
	}

	return
}

func (p *parser) badExpr() *BadExpr {
	b := new(BadExpr)
	b.pos = p.pos()
	return b

	public static final field Companion Lokhttp3/MultipartBody$Companion;
	public static final field DIGEST Lokhttp3/MediaType;
	public static final field FORM Lokhttp3/MediaType;
	public static final field MIXED Lokhttp3/MediaType;
	public static final field PARALLEL Lokhttp3/MediaType;
	public final fun -deprecated_boundary ()Ljava/lang/String;
	public final fun -deprecated_parts ()Ljava/util/List;

// that the calls are properly synchronized on the Go side.
//
// To be clear, if the calls are not properly synchronized on the Go side,
// we will be hiding races. But when using TSAN on mixed Go C/C++ code
// it is more important to avoid false positives, which reduce confidence
// in the tool, than to avoid false negatives.
const yesTsanProlog = `
#line 1 "cgo-tsan-prolog"

  // CHECK: return %[[CLUSTER_RES]]#0
  func.return %1 : tensor<*xi32>
}

// -----

// Tests that resource ops with both load and store are hoisted
// but input to load and output from store have mixed defined/undefined shapes.

// CHECK-LABEL: func @same_resource_load_and_store_cast
func.func @same_resource_load_and_store_cast() -> tensor<1xi32> {

  // CHECK: %[[RES_HANDLE:[0-9]*]] = "tf.VarHandleOp"

// * Nothing. This is managed, with IP auto assigned
//
// Not supported:
// Multiple hostname/IP - It is feasible but preference is to create multiple Gateways. This would also break the 1:1 mapping of GW:Service
// Mixed hostname and IP - doesn't make sense; user should define the IP in service
// NamedAddress - Service has no concept of named address. For cloud's that have named addresses they can be configured by annotations,
//

				} else {
					msg = "missing type parameter name"
					// go.dev/issue/60812
					if len(list) == 1 {
						msg += " or invalid array length"
					}
				}
			} else {
				msg = "mixed named and unnamed parameters"
			}
			p.error(errPos, msg)
		}
	}

	// Convert list to []*ast.Field.
	// If list contains types only, each type gets its own ast.Field.
	if named == 0 {

Both approaches are acceptable, but you should create and follow a convention to ensure consistency across your build files.

[NOTE]
====
Don't get your `into()` specifications mixed up.
For a normal copy, one to the filesystem rather than an archive, there should always be _one_ "root" `into()` that specifies the overall destination directory of the copy.

	// If ALL instances have a sidecar, we enable TLS, otherwise we disable
	// TODO(https://github.com/istio/istio/issues/27376) enable mixed deployments
	// A service with passthrough resolution is always passthrough, regardless of the TrafficPolicy.
	if service.Resolution == Passthrough || tp.GetLoadBalancer().GetSimple() == networking.LoadBalancerSettings_PASSTHROUGH {