{"id":150561,"date":"2021-06-04T14:22:14","date_gmt":"2021-06-04T13:22:14","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=go&p=150561"},"modified":"2021-06-18T14:29:42","modified_gmt":"2021-06-18T13:29:42","slug":"goland-2021-2-eap-build-2-is-here","status":"publish","type":"go","link":"https:\/\/blog.jetbrains.com\/zh-hans\/go\/2021\/06\/04\/goland-2021-2-eap-build-2-is-here","title":{"rendered":"GoLand 2021.2 EAP Build #2 Is Here!"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

GoLand 2021.2 EAP build #2 is out and ready for you to install!<\/p>\n\n\n\n

You can get the EAP build via the Toolbox App<\/a>, download it from our website<\/a>, use a snap package (for Ubuntu), or from inside GoLand, select Automatically check updates for Early Access Program<\/em> in Preferences \/ Settings | Appearance & Behavior | System Settings | Updates<\/em>.<\/p>\n\n\n\n

Download GoLand 2021.2 EAP #2<\/a><\/p>\n\n\n\n

Download modules on demand <\/h2>\n\n\n\n

GoLand has the Sync dependencies<\/em> action, which fetches missed dependencies and removes unused ones by calling go mod tidy\/vendor<\/em>. It works a little bit differently with replace<\/em> directives in go.mod<\/em> files. <\/p>\n\n\n\n

Earlier, if you specified a module that wasn\u2019t used anywhere in your code (but you still wanted to have it) in the replace <\/em>directive, the IDE wouldn\u2019t download or delete it, and the lines with these unused dependencies would be marked red. It didn\u2019t affect how the application worked, but those red lines have been confusing our users and causing them to look for errors. <\/p>\n\n\n\n

This new feature will help resolve such situations. If you run Sync dependencies <\/em>and you still see red lines in the go.mod<\/em> file, click on the red bulb or use Option + Enter (Alt + Enter)<\/em>. You will see a couple of options apart from Sync dependencies <\/em>\u2013 download a particular module or all the specified modules to your cache. <\/p>\n\n\n\n

In a future EAP build, we\u2019re also planning to mark differently any modules that are not required by your code or any of its dependencies. These lines will be highlighted as unused.\u00a0\u00a0<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Support for generics in .go files<\/h2>\n\n\n\n

Last June, the Go team announced a draft design for generics, a.k.a. type parameters. In March 2021, this draft design became a proposal. Generics should be available in the Go 1.18 release in early 2022. <\/p>\n\n\n\n

Since GoLand 2020.2, we\u2019ve been providing experimental support for generics. You can play with them by turning on the Enable experimental support for generics a.k.a. type parameters<\/em> setting in Settings\/Preferences | Go<\/em>. The details about how to use type parameters in GoLand are available in our documentation<\/a>. <\/p>\n\n\n\n

Previously, experimental support for generics in GoLand was only available in files with the .go2 <\/em>extension. It was done this way so that this experiment wouldn\u2019t interfere with the rest of the work. If you wrote some code with generics in .go <\/em>files, the IDE would suggest renaming them with the .go2<\/em> extension. <\/p>\n\n\n\n

We now think that experimental generics support in GoLand is stable enough, so with this EAP release GoLand provides support for type parameters in .go<\/em> files, too. It no longer suggests renaming the file, but you still need to enable support for generics in the settings or through a quick-fix.\u00a0<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Clearer messages about settings mismatch <\/h2>\n\n\n\n

This feature suggests an explicit call to action if the settings of the target system in your project don\u2019t match your code.  <\/p>\n\n\n\n

Let\u2019s say you imported the \u201cC\u201d<\/em> package, which allows calling C code from Go, but didn\u2019t enable cgo<\/em> support in the project settings. <\/p>\n\n\n\n

The IDE will suggest Navigate to cgo import<\/em>, which will put the cursor right before the package\u2019s name. You can also Enable cgo support <\/em>with one click without needing to go to Preferences\/Settings | Go | Build Tags and Vendoring.<\/em> As earlier, there is an option to Edit Go project settings. <\/em>It opens a window with the settings for Build Tags and Vendoring<\/em>. \u00a0\u00a0<\/em><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Find implementations of \u201cinternal\u201d interfaces easily <\/h2>\n\n\n\n

Starting with this release, you can Navigate to implementations<\/em> of the interfaces contained in the internal<\/em> folder. To jump to the implementations, click on the gutter. You can also jump back to the interface from its implementations.\u00a0\u00a0<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Version control improvements <\/h2>\n\n\n\n

This EAP release brings you some new pre-commit checks. You can now Run tests<\/em> and Analyze code<\/em> before committing your changes. Go to Preferences\/Settings | Version Control | Commit | Before commit <\/em>or click on the gear icon in the Commit<\/em> view. <\/em>GoLand will show the progress and the results of pre-commit checks in the Commit<\/em> area without opening additional modal windows.\u00a0\u00a0<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

We\u2019ve also improved the Local History<\/em> menu, which helps you track all changes independently of version control. We\u2019ve added a new search field here to quickly find necessary text in your Local History<\/em> revisions. To try it, right-click on the file and go to Local History | Show History<\/em>.\u00a0<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

New terminal options <\/h2>\n\n\n\n

Some of you probably have always wanted to use the underline <\/em>or vertical<\/em> cursor shape in our built-in terminal \u2013 we made it happen! To change it, go to Preferences\/Settings | Tools | Terminal<\/em>.<\/p>\n\n\n\n

There is also one new option in the Terminal <\/em>settings: we now support Use Option as Meta key<\/em>. <\/p>\n\n\n\n

This may sound familiar \u2013 macOS native terminal has this option. The Meta key temporarily modifies the normal action of another key when they are pressed together. For instance, you can now use the following shortcuts when working in the terminal: <\/p>\n\n\n\n