{"id":155284,"date":"2021-06-17T14:27:58","date_gmt":"2021-06-17T13:27:58","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=go&p=155284"},"modified":"2022-05-23T18:02:29","modified_gmt":"2022-05-23T17:02:29","slug":"goland-2021-2-eap-build-4-is-here","status":"publish","type":"go","link":"https:\/\/blog.jetbrains.com\/zh-hans\/go\/2021\/06\/17\/goland-2021-2-eap-build-4-is-here","title":{"rendered":"GoLand 2021.2 EAP Build #4 Is Here!"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

GoLand 2021.2 EAP Build #4 is out. <\/p>\n\n\n\n

You can get this EAP build via the Toolbox App, download it from our website, use a snap package (for Ubuntu), or get it right in GoLand by selecting 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 #4<\/a><\/p>\n\n\n\n

Support for converting a slice to an array pointer<\/h2>\n\n\n\n

The Go 1.17 release date is approaching, and in this version, it will be possible to convert a slice to an array pointer<\/a>. Before, it was only possible to do this kind of conversion with the help of the unsafe<\/em> package, which allows stepping around type safety in Go. <\/p>\n\n\n\n

As the 1.17 draft release notes<\/a> say: <\/p>\n\n\n\n

Converting a slice to an array pointer yields a pointer to the underlying array of the slice. If the length of the slice is less than the length of the array, a run-time panic occurs.<\/p><\/blockquote>\n\n\n\n

Since Go 1.17 will allow you to convert a slice into an array pointer, GoLand will not mark these conversions as errors. To do this, change GOROOT to \u201cGo 1.17beta1\u201d in Preferences\/Settings | Go<\/em>. <\/p>\n\n\n\n

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

Generic support for web-types<\/h2>\n\n\n\n

There are some important changes for front-end technologies in this build. We are introducing a new version of web-types \u2013 an open-source standard for documenting various web frameworks. Its initial version was focused only on Vue.js support. This blog post<\/a> from the WebStorm team describes web-types in more detail. <\/p>\n\n\n\n

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

With this release, we want to build a new architecture to make it easier to support new JavaScript frameworks and extend support for the existing ones. There might be some regressions around Vue.js support while the migration is still in progress. We\u2019re hoping to stabilize this functionality in the next couple of weeks. Please let us know if you spot any issues! <\/p>\n\n\n\n

Support for TypeScript types in JSDoc comments<\/h2>\n\n\n\n

GoLand now properly supports the TypeScript syntax used within JSDoc comments in your .js<\/em> files. Support for some syntactic constructs, such as union types, has already been available for a while. <\/p>\n\n\n\n

With this release, the existing support has been reworked and expanded. The IDE recognizes more syntactic constructs, and we\u2019ve fixed a lot of known issues, too. For example, optional properties in @typedef <\/em>declarations are now supported. <\/p>\n\n\n\n

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

Intelligent spelling and grammar checks in Go files<\/h2>\n\n\n\n

We\u2019ve also enabled intelligent spelling and grammar checks in Go files by default. These checks are provided by the Grazie plugin, which is bundled with the IDE. To adjust the settings, go to Preferences\/Settings | Editor | Proofreading | Grammar<\/em>, where you will find the Scope<\/em>, Rules<\/em>, and Exceptions<\/em> sections.<\/p>\n\n\n\n

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

Other improvements and bug-fixes<\/h2>\n\n\n\n

\u2013 GO-11233<\/a> \u2013 GoLand will suggest creating new Go modules projects in the ~\/GolandProjects<\/em> directory. <\/p>\n\n\n\n

\u2013 GO-10730<\/a> \u2013 -coverpkg<\/em> is not added when running tests on .\/…<\/em>; this temporary fix is needed because of this issue with Go<\/a>. <\/p>\n\n\n\n

That\u2019s all for today. You can find the complete list of improvements for this EAP build in the release notes<\/a>. Please tell us what you think about our new features. You can share your feedback here in the comments, on Twitter<\/a>, or in the Gophers Slack<\/a> #goland channel. You can also open a ticket in our issue tracker<\/a>.<\/p>\n","protected":false},"author":1254,"featured_media":150564,"comment_status":"closed","ping_status":"closed","template":"","categories":[826],"tags":[6569,600],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/go\/155284"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/go"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/types\/go"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/users\/1254"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/comments?post=155284"}],"version-history":[{"count":10,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/go\/155284\/revisions"}],"predecessor-version":[{"id":248900,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/go\/155284\/revisions\/248900"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/media\/150564"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/media?parent=155284"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/categories?post=155284"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/tags?post=155284"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/cross-post-tag?post=155284"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}