Automatically Define GOPATH for Individual Projects

Introduction:
Managing dependencies and projects in Go requires setting the GOPATH environment variable, but the default approach of using a single GOPATH can lead to conflicts and redundancy. This discussion explores potential solutions for defining GOPATH on a per-project basis.

Defining GOPATH per Project:
The traditional approach requires manually setting GOPATH for each project using the export GOPATH={path_to_project} command. This manual process can be tedious and error-prone.

Bash Configuration:
One solution involves creating a .bashrc or .bash_profile file for each directory, defining GOPATH for that specific project. This approach allows for automated GOPATH configuration upon entering a project directory.

Visual Studio Code Integration:
An alternative approach offered by Visual Studio Code (VSCode) is to utilize the "Go for Visual Studio Code" extension. This extension allows you to set a global GOPATH while inferring a separate, project-specific GOPATH within VSCode. This provides a convenient way to manage project dependencies without modifying the global GOPATH.

Future Developments:
With the introduction of modules in Go 1.11, the use of GOPATH may become deprecated in favor of a project-based workflow. This would eliminate the need for manual GOPATH configuration on a per-project basis.

Conclusion:
Defining GOPATH on a per-project basis provides greater organization and flexibility when managing Go projects. The presented solutions, including bash scripts, VSCode integration, and the potential deprecation of GOPATH, offer various options to address this need.