println("expect: OK")
		CoroLockOSThread(callerExhaustLocked, iterSimple)
	})
	register("CoroLockOSThreadLockIterNested", func() {
		println("expect: OK")
		CoroLockOSThread(callerExhaustLocked, iterNested)
	})
	register("CoroLockOSThreadLockIterLock", func() {
		println("expect: OK")
		CoroLockOSThread(callerExhaustLocked, iterLock)
	})
	register("CoroLockOSThreadLockIterLockYield", func() {

	register("CoroCgoCallback", func() {
		println("expect: OK")
		CoroCgo(callerExhaustCallback, iterSimple)
	})
	register("CoroCgoCallbackIterNested", func() {
		println("expect: OK")
		CoroCgo(callerExhaustCallback, iterNested)
	})
	register("CoroCgoCallbackIterCallback", func() {
		println("expect: OK")
		CoroCgo(callerExhaustCallback, iterCallback)
	})
	register("CoroCgoCallbackIterCallbackYield", func() {

BoringCrypto (the core of [BoringSSL](https://boringssl.googlesource.com/boringssl/))
for various crypto primitives, in furtherance of some work related to FIPS 140.
We have heard that some external users of Go would be
interested in this code as well, so we have published this code
here in the main Go repository behind the setting GOEXPERIMENT=boringcrypto.

Use of GOEXPERIMENT=boringcrypto outside Google is _unsupported_.

## Modify test for regression search

First, you should change the test so that
 - only the version you are interested in is used as a reference
 - only the test you are interested in is executed
 - tighten the regression limits to get significant results
 - only search for memory/execution time regressions depending on what you are interested in
 

 */
public interface FileCollectionStructureVisitor {
    enum VisitType {
        // Visitor is interested in the contents of the collection
        Visit,
        // Visitor is not interested in the contents of the collection, but would like to receive the source and other metadata
        NoContents
    }

    /**

        assertTestExecuted(className: 'example2.MyOtherTest2', methodName: 'baz', task: ':secondTest')

        when:
        events.clear()
        stdout.reset() // we are interested in the output of the second build only
        launchTests { TestLauncher launcher ->
            launcher.withArguments("--configuration-cache")
            launcher.withTestsFor { TestSpecs specs ->

// nobody will tell us anymore.
//
// Beside calling runtime·netpollopen, the networking code paths
// will call runtime·netpollarm each time goroutines are interested
// in doing network I/O. Because now we know what kind of I/O we
// are interested in (reading/writing), we can call port_associate
// passing the correct type of event set (POLLIN/POLLOUT). As we made
// sure to have already associated the file descriptor with the port,

# In addition to the above, test to make sure there is no funny
# business if we try "go test -cover" in atomic mode targeting
# sync/atomic itself (see #57445). Just a short test run is needed
# since we're mainly interested in making sure the test builds and can
# execute at least one test.

go test -short -covermode=atomic -run=TestStoreInt64 sync/atomic
go test -short -covermode=atomic -run=TestAnd8 internal/runtime/atomic

            throws ArtifactMetadataRetrievalException;

    /**
     * Get a list of available versions for an artifact in the remote repository
     *
     * @param artifact           artifact we are interested in. Only <code>groupid</code> and <code>artifactId</code>
     *                           are needed, for instance the following code will work

== Next steps

Building a library is just one aspect of reusing code across project boundaries.
From here, you may be interested in:

 - link:{userManualPath}/building_java_projects.html[Building Java & JVM projects]
 - link:{userManualPath}/java_library_plugin.html[Java Library Plugin documentation]