Creating specific test environments - When testing for backward compatibility or ensuring the success of bug fixes it is important to control for runtime version.Differing requirements among projects - When switching between working on multiple projects, it is often necessary to use different Go versions for each.There are a few scenarios where I’ve found it beneficial to have more than one version available: An alternative approach involves setting your terminal’s PATH environment variable to point to a specific Go version’s SDK. This is simple for getting started, but also can be limiting.Ī more flexible set up is to enable running multiple versions within the same environment via go1.17 or go1.18 commands, for example. Out of the box, installing Go means you have a single go command you can run to build and test your project. Let’s go! When Do We Need Multiple Go Versions? Finally, we’ll conclude with a discussion of why this approach is so powerful. In this post I’ll present the when and the how of enabling multiple Go versions. If this is something you’ve tried or have considered, great! As a user of the Go programming language, I’ve found it useful to enable the running multiple versions within a single project.
0 Comments
Leave a Reply. |