The second construct of our 2022.3 Early Entry Program is out now.
You will get the EAP construct by way of the Toolbox App, obtain it from our web site, use a snap package deal (for Ubuntu), or from inside GoLand, choose Verify IDE updates for Early Entry Program in Preferences / Settings | Look & Habits | System Settings | Updates.
The Go Workspace File motion
Within the New context menu, you’ll now discover the Go Workspace File motion. Choose it, and a go.work file will seem in your root folder. Current Go modules will routinely be added to the go.work file.
The Go playground inside GoLand
We’ve applied a characteristic that simulates the Go playground performance inside GoLand.
You possibly can choose a chunk of code, select the Open in choice after which click on Playground. It will open a scratch file with a toolbar which comprises the identical choices you might have when utilizing the Go playground.
You possibly can format and share your code, change the Go model, run your code utilizing the Go playground server, or run it domestically.
You even have the choice to load the code from a file or from a Go playground URL.
Efficiency enhancements
‘go checklist’ modifications
While you open a venture, GoLand indexes the recordsdata and runs the go checklist command, which studies details about the venture construction, for instance, which dependencies and modules the venture comprises. Indexing is paused whereas go checklist is working, and also you don’t have entry to code perception options till indexing is completed.
Beforehand, the go checklist command would run twice in some circumstances. This occurred as a result of, after the primary run, GoLand would acknowledge that the venture had modified with out with the ability to inform whether or not there have been any new modules. A second go checklist run was then wanted to establish whether or not there have been new modules within the venture that needs to be checked.
We’ve modified our API, so now the IDE discovers whether or not new modules have appeared within the venture instantly after the primary time go checklist is run. Any more, go checklist will solely be launched a second time if new modules are detected within the venture.
We hope that this modification will considerably enhance efficiency for giant tasks with a whole lot of modules.
Restore venture construction from cache on open
This variation additionally issues how GoLand indexes recordsdata and runs the go checklist command.
As we already talked about, once you open a venture, GoLand indexes the recordsdata and runs go checklist. Whereas go checklist is working, indexing is paused, and code perception options gained’t work till it’s completed.
Now, once you open a venture, the knowledge reported by go checklist is saved on disk in cache reminiscence. While you open that venture once more, the information in regards to the venture’s construction is loaded from reminiscence and thought of when indexing begins.
Due to this, indexing continues with out pauses and finishes sooner. go checklist nonetheless must be launched, but it surely runs within the background. On account of these modifications, the code perception options can be found a lot sooner after you open the venture.
Quicker IDE startup and venture opening
GoLand has acquired various different efficiency enhancements designed to lower the time it takes to launch functions and open tasks in JetBrains IDEs.
A number of the processes that used to run sequentially have been parallelized. The crew has additionally managed to cut back keen class loading and save vital time on Intention Actions, Inspections, some constants, and different extensions that have been beforehand loaded and instantiated unnecessarily.
Practically all venture parts in bundled plugins have been eradicated. Consequently, total startup efficiency – together with editor restoration – has been improved by round 30%.
File measurement restrict raised
We’ve raised the file measurement restrict from 2.5 MB to 10 MB.
Code perception options, like navigation and highlighting, don’t work for recordsdata that exceed the dimensions restrict. Whereas the two.5 MB restrict was sufficient for many recordsdata, there are tasks with recordsdata larger than that – as an illustration, the AWS SDK or GCP.
We expect 10 MB will cowl all the favored SDKs. If it’s not sufficient for you, please depart your suggestions right here.
That’s it for at present! We’d love to listen to what you concentrate on the brand new options. Ping us on Twitter, depart your feedback right here, open a problem in our tracker, or drop us a message within the Gophers Slack #goland channel. Thanks for studying!
