The new [Preorder] function returns a convenient iterator over all the

plugins {
    id("gradlebuild.distribution.implementation-kotlin")
    id("gradlebuild.kotlin-dsl-sam-with-receiver")
}

description = "Kotlin extensions to make working with Gradle :core and family more convenient"

dependencies {
    api(projects.core)
    api(projects.coreApi)
    api(projects.files)
    api(projects.hashing)

    api(libs.kotlinStdlib)

    implementation(projects.baseServices)
    implementation(projects.messaging)

It contains a group of named constants (variables) with integer status codes.

For example:

* 200: `status.HTTP_200_OK`
* 403: `status.HTTP_403_FORBIDDEN`
* etc.

It can be convenient to quickly access HTTP (and WebSocket) status codes in your app, using autocompletion for the name without having to remember the integer status codes by memory.

# Helm Profiles

This folder provides a variety of "profiles" for helm installation.
While a user can just explicitly pass this with `--values/-f`.

However, Istio also provides a feature to bundle these with the charts, which is convenient when installing from remote charts.
For details, see `copy-templates` Makefile target, and `manifests/zzz_profile.yaml`.

Any changes to this folder should have a `make copy-templates` applied afterwards.

/**
 * The set of {@link IvyConfiguration}s that will be included in the {@link IvyPublication}.
 *
 * Being a {@link org.gradle.api.NamedDomainObjectContainer}, a {@code IvyConfigurationContainer} provides
 * convenient methods for adding, querying, filtering, and applying actions to the set of {@link IvyConfiguration}s.
 *
 * <pre class='autoTested'>
 * plugins {
 *     id 'ivy-publish'
 * }
 *

// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

// This file and importx_test.go make it possible to write tests in the runtime
// package, which is generally more convenient for testing runtime internals.
// For tests that mostly touch public APIs, it's generally easier to write them
// in the runtime_test package and export any runtime internals via
// export_test.go.
//

package http

import (
	"io"

	xioutil "github.com/minio/minio/internal/ioutil"
)

// DrainBody close non nil response with any response Body.
// convenient wrapper to drain any remaining data on response body.
//
// Subsequently this allows golang http RoundTripper
// to reuse the same connection for future requests.
func DrainBody(respBody io.ReadCloser) {

import org.gradle.api.DomainObjectSet;

/**
 * A Collection of {@link IvyArtifact}s to be included in an {@link IvyPublication}.
 *
 * Being a {@link DomainObjectSet}, an {@code IvyArtifactSet} provides convenient methods for querying, filtering, and applying actions to the set of {@link IvyArtifact}s.
 *
 * <pre class='autoTested'>
 * plugins {
 *     id 'ivy-publish'
 * }
 *

import org.gradle.api.DomainObjectSet;

/**
 * A Collection of {@link MavenArtifact}s to be included in a {@link MavenPublication}.
 *
 * Being a {@link DomainObjectSet}, a {@code MavenArtifactSet} provides convenient methods for querying, filtering, and applying actions to the set of {@link MavenArtifact}s.
 *
 * <pre class='autoTested'>
 * plugins {
 *     id 'maven-publish'
 * }
 *

// Tags always returns nil.
func (s allSubtags) Tags() []Tag {
	return nil
}

// coverage is used by NewCoverage which is used as a convenient way for
// creating Coverage implementations for partially defined data. Very often a
// package will only need to define a subset of slices. coverage provides a
// convenient way to do this. Moreover, packages using NewCoverage, instead of
// their own implementation, will not break if later new slice types are added.