– GO-12171 – The “Cannot use … (type …) as the type any” error has been fixed. In this release, you will also find some notable bug-fixes, such as: GoLand now reports an unused variable passed to a closure as an error if you set your Go SDK to 1.18. Unused variable passed to a closure is reported as an error In the dropdown list, go to Go | Code style issues. If you want to change the severity level, go to Preference/Settings | Editor | Code Style | Inspections. With that severity level, the inspection will not highlight the code, but you will still be able to get the “Add comment” quick-fix. The severity level of that inspection is “No highlighting, only fix”. We’ve enabled by default an inspection that checks whether you added a comment to your exported element. The “Exported element should have a comment” inspection is enabled by default Support for underlying type constraintsįunctions with underlying type constraints are now supported, and GoLand no longer shows a “missing function body” error. GoLand also checks the Go version in your go.mod file and suggests a quick-fix to change it if you use generics and the Go version is incompatible with generics. You can try this and some other generics-related features in our Generics (type parameters) lesson that is available on the Welcome screen in the Learn GoLand section. If you don’t have the 1.18 version, it will be suggested to download. If your project contains generics, but Go SDK for this project is lower than 1.18, GoLand will suggest a quick-fix for switching to the 1.18 version. Quick-fix for switching to a newer Go SDK You can download the build from the website, update via the Toolbox App, apply a patch (go to GoLand | Check for Updates), or use a snap package (for Ubuntu).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |