package b

-- b/b_test.go --
package b

import (
  _ "a/x/internal/y"
)

-- depends-on-a/depends-on-a.go --
// A package that depends on a package with a bad import
package depends

import (
  _ "a"
)

-- depends-on-a/depends-on-a_test.go --
package depends

import (
  _ "a"
)

-- a/x/internal/y/y.go --

example.com/depends/on/generics v1.0.0
written by hand

-- .mod --
module example.com/depends/on/generics

go 1.18

require example.com/generics v1.0.0
-- .info --
{"Version":"v1.0.0"}
-- go.mod --
module example.com/depends/on/generics

go 1.18

require example.com/generics v1.0.0
-- main.go --
package main

import "example.com/generics"

# package-import cycles that are not possible in an ordinary build. This test
# verifies that such cycles are handled even when they cross module boundaries.

# First, verify that the import graph depends on build tags as expected.
go list -deps example.com/left
stdout '^example.com/right$'
go list -deps example.com/right
! stdout left

env GOFLAGS=-tags=mirror
go list -deps example.com/left
! stdout right

# "runtime/cgo [runtime.test]" appears in the test dependencies of "runtime",
# because "runtime/cgo" itself depends on "runtime"

go list -deps -test -compiled -f '{{if eq .ImportPath "net [runtime.test]"}}{{printf "%q" .Imports}}{{end}}' runtime

	# Control case: the explicitly-imported package "sync" is a test variant,
	# because "sync" depends on "runtime".
stdout '"sync \[runtime\.test\]"'
! stdout '"sync"'

# Regression test for https://golang.org/issue/41113.
#
# When resolving a missing import path, the inability to add the package from
# one module path should not interfere with adding a nested path.

# Initially, our module depends on split-incompatible v2.1.0-pre+incompatible,
# from which an imported package has been removed (and relocated to the nested
# split-incompatible/subpkg module). modload.QueryPattern will suggest

# because the checksumOk function was failing because modfetch.GoSumFile
# was not set when running outside of a module.

env GOTOOLCHAIN=local

cd $GOPATH/src/link
go mod init
stderr link
rm go.mod

# Too hard: doesn't match unevaluated nor completely evaluated. (Only partially evaluated.)
# Whether this works depends on which OS we are running on.
# cd $WORK/gopath/src/link
# ! go mod init

-- $WORK/x/x.go --
package x // import "x"

-- $GOPATH/src/example.com/x/y/y.go --
package y
-- $GOPATH/src/example.com/x/y/z/z.go --

# a clone of gopkg.in/[…].vN should be replaceable by
# a fork hosted at corp.example.com/[…]/vN,
# even if there is an explicit go.mod file containing the
# gopkg.in path.

skip 'skipping test that depends on an unreliable third-party server; see https://go.dev/issue/54503'
	# TODO(#54043): Make this test hermetic and re-enable it.

[!net:gopkg.in] skip
[!git] skip

env GO111MODULE=on
env GOPROXY=direct

go get example.net/ambiguous/nested/pkg@v0.1.0
go list -m all
stdout '^example.net/ambiguous/nested v0.1.0$'
! stdout '^example.net/ambiguous '


# From an initial state that already depends on the shorter path,
# the same 'go get' command should (somewhat arbitrarily) keep the
# existing path, since it is a valid interpretation of the command.

cp go.mod.orig go.mod

go mod edit -replace=example.com/c@v0.0.0=../../outside/c
go install example.com/c
go version -m $GOBIN/c$GOEXE
! stdout vcs.revision
rm $GOBIN/c$GOEXE
exec git checkout go.mod

# If the build depends on a package in the repository, but it's not in the
# main module, there should be no VCS info.
go mod edit -require=example.com/b@v0.0.0
go mod edit -replace=example.com/b@v0.0.0=../b