Why Am I Getting a 'Use of Internal Package Not Allowed' Error in Go?

Understanding "Use of Internal Package Not Allowed" Error

When attempting to build and run a project, you may encounter the "use of internal package not allowed" error, indicating that you're attempting to import a package that falls within the scope of an "internal" folder. This error prevents importing internal packages from external packages.

Nature of Internal Packages

Internal packages serve as private containers within Go projects. They can be imported only by packages that reside within the same directory level as the internal folder, or by packages that are directly above the directory containing the internal folder.

Resolving the Error

To resolve this error, it's important to understand the following rules:

• Internal packages cannot be imported by packages outside their parent directory.
• The problem with the consensus.go file is that it attempts to import the github.com/hyperledger/fabric/internal/pkg/identity package, which is defined as an internal package. Since the consensus.go file resides in a different directory, this import is not permitted.

Solutions

You have two options to resolve this error:

1. Reorganize the Package Structure: If you require access to the functionality contained in the internal package, you can move the consensus.go file into the same directory as the internal package. This will allow the import to succeed.
2. Create a Public Equivalent: Alternatively, you can create a public version of the functionality that you need from the internal package. This involves creating a new package outside the internal folder that provides the same interfaces and functions. You can then import this public package into the consensus.go file.

By adhering to these principles, you can effectively resolve the "use of internal package not allowed" error and continue developing your project.

The above is the detailed content of Why Am I Getting a 'Use of Internal Package Not Allowed' Error in Go?. For more information, please follow other related articles on the PHP Chinese website!