{"id":596699,"date":"2025-09-08T19:05:06","date_gmt":"2025-09-08T18:05:06","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=go&p=596699"},"modified":"2025-09-15T15:53:33","modified_gmt":"2025-09-15T14:53:33","slug":"goland-can-do-that-ten-secret-superpowers-you-might-not-know","status":"publish","type":"go","link":"https:\/\/blog.jetbrains.com\/zh-hans\/go\/2025\/09\/08\/goland-can-do-that-ten-secret-superpowers-you-might-not-know","title":{"rendered":"\u201cGoLand Can Do That?\u201d Ten Secret Superpowers You Might Not Know"},"content":{"rendered":"\n

Note: This is a guest post from John Arundel, a Go writer and teacher who blogs at <\/em>bitfieldconsulting.com<\/em><\/a>. His most recent book is <\/em>The Deeper Love of Go<\/em><\/a>.<\/p>\n\n\n\n

How do you break it to someone that they’ve wasted most of their life? Well, I worked with a guy who didn’t know how to copy and paste. Every time he wanted to move some code, he’d delete it and then grimly re-type the whole thing somewhere else, as I watched in silent dismay: \u201cHow do I tell him?\u201d<\/p>\n\n\n\n

It wasn’t that he didn’t want to be able to copy and paste. He just had no idea that he could \u2013 he’d never taken the time to fiddle around and find out.<\/p>\n\n\n\n

That guy is all of us, in a way. Even if we can copy and paste, what other editor superpowers are we missing out on? And how much time are we wasting by not knowing about them? I’m just going to confidently say \u201cSome\u201d, right?<\/p>\n\n\n\n

A modern IDE is more than just a text editor \u2013 it’s also a file manager, debugger, linter, AI assistant, and so on. Even better, an IDE like GoLand<\/a> actually understands Go<\/em>, so it can make suggestions as you type, highlight errors, annotate your code, and refactor automatically.<\/p>\n\n\n\n

Here are ten things you might not know GoLand can do, and each one will make you more productive as a Go developer.<\/p>\n\n\n\n

Search everywhere<\/h2>\n\n\n\n

90% of software engineering is just finding stuff, I reckon: where is that function defined? Where did I put that struct type?<\/p>\n\n\n\n

Double-tap the Shift<\/em> key in GoLand and type to search everywhere\u201d: definitions, symbols, filenames, or even editor features. For example, enter search<\/code> to see all search-related settings.<\/p>\n\n\n\n

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

Go to implementation<\/h2>\n\n\n\n

Cmd-click<\/em> a function or variable name and GoLand will take you straight to its definition, even in another package or file (or even the standard library or your dependencies). And you can keep drilling down further until you find what you need, then use Cmd-[<\/em> to jump back.<\/p>\n\n\n\n

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

Structure view<\/h2>\n\n\n\n

For a high-level overview of your constants, functions, types, and their associated methods, press Cmd-F12<\/em> to open the Structure<\/em> view of your file or package. Click on any item to go to its definition.<\/p>\n\n\n\n

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

Parameter names<\/h2>\n\n\n\n

GoLand shows inline hints for function calls, giving parameter names for each function argument. This makes reading code easier, especially when arguments are nil<\/code>, for example. You’ll also see name hints for results in a return<\/code> statement, and field names for struct literals that omit them.<\/p>\n\n\n\n

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

Errors and warnings<\/h2>\n\n\n\n

Sure, GoLand can point out compile errors \u2013 an angry red underline indicates the offending code, and you can hover the mouse over it to see what’s wrong (or use the Inspection Lens plugin to see all errors inline without hovering). Saved you a compile-edit-fix cycle.<\/p>\n\n\n\n

That’s great, but GoLand will also warn you about probable mistakes: unreachable code, unhandled errors, unused functions, redundant type conversions, or variable names that shadow the name of a package. Even though they’re technically legal (the best kind of legal), they’re likely not what you meant, and GoLand will pick these up and offer to auto-fix them.<\/p>\n\n\n\n

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

Nil<\/code> pointer analysis<\/h2>\n\n\n\n

Ah, pointers! The cause of \u2013 and solution to \u2013 all programming problems. Specifically, pointers can be nil<\/code> (meaning \u201cdoesn’t point to any value\u201d). That’s a problem if you try to dereference such a pointer (that is, ask Go to give you the value it points to), and by \u201cproblem\u201d I mean \u201chorrible crash\u201d.<\/p>\n\n\n\n

But how can you tell whether a pointer will be nil<\/code> at run time without running the program? Only by understanding the complete history of that variable throughout the code. Unfortunately, even GoLand isn’t yet smart enough to *touches earpiece*<\/em> and I’m being told that in fact GoLand is now smart enough to do that.<\/p>\n\n\n\n

The experimental data flow analysis<\/em> feature<\/a> simulates the execution of your program to catch run-time errors like nil<\/code> pointers even before you run it. That’s something I’ve never seen before in an IDE, and it’s pretty impressive.<\/p>\n\n\n\n

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

Completions and templates<\/h2>\n\n\n\n

You’d expect GoLand to offer inline completions of function and variable names and so on, but that’s table stakes. Even more powerful are live templates: parameterized code snippets you can insert and complete interactively.<\/p>\n\n\n\n

For example, if you want to write a for ... range<\/code> loop, type for<\/code>, and select For range loop<\/em> from the picklist (or type forr<\/code> and press Tab). You’ll get a skeleton for<\/code> loop with placeholders for you to fill in the loop variables and body.<\/p>\n\n\n\n

Similarly, if you get bored typing if err != nil...<\/code> repeatedly (but how could anyone find that boring?) GoLand can fill in the error-handling block for you, if you ask nicely.<\/p>\n\n\n\n

Live templates automate dozens of the most common Go patterns and idioms, and you can create your own, with placeholders like $INDEX$<\/code> for parameters you want users to fill in.<\/p>\n\n\n\n

Also, if you have a blob of JSON data that you need to turn into a Go type, just paste it into the editor. GoLand will offer to generate the struct definition for you automatically, complete with json<\/code> tags to make it parseable.<\/p>\n\n\n\n

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

Refactoring<\/h2>\n\n\n\n

Do you ever wish you’d named your child something different? It might be a bit late to revisit that one, but fortunately it’s always possible to rename things in your Go programs, like functions and variables.<\/p>\n\n\n\n

Manually retyping them everywhere would be annoying, and normal search-and-replace is error-prone (the Scunthorpe<\/a> problem). GoLand is smarter about this because it understands Go: it knows if a word is a variable or function name, and avoids replacing it if it’s in some other context like inside a string or a comment.<\/p>\n\n\n\n

Also, you can edit a function’s signature, adding or removing parameters as you like, and GoLand will automatically change the calls to that function everywhere.<\/p>\n\n\n\n

Or try this one weird tip to slim down your chubby functions, and make your code beach body ready: select some lines and use Extract method<\/em> to replace them with a call to a method that does the same thing. By eliminating paperwork, you make the program more readable and focus on what’s actually relevant.<\/p>\n\n\n\n

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

Debugging<\/h2>\n\n\n\n

Now, I’m not saying you ever write bugs \u2013 perish the thought. Shall we say rather that programs occasionally don’t behave exactly the way we expect them to? Figuring out just where and why things are going wrong can be difficult, unless you can shrink down to the size of an electron and go inside the computer to see what’s happening (I’m still waiting on that Kickstarter).<\/p>\n\n\n\n

Failing this, though, GoLand’s debugger is a pretty acceptable substitute. For example, set a breakpoint on a suspicious line and the debugger will stop the program there, keeping all variables intact so that you can inspect them (or edit them). Breakpoints can be conditional, too, so you only stop if a certain expression is true.<\/p>\n\n\n\n

Then, if the problem still isn’t clear, you can Step Over<\/em> to continue executing the code line by line, or Step Into<\/em> to follow function calls down the rabbit hole.<\/p>\n\n\n\n

To get really inside baseball, you can set a watch<\/em> on the variables you’re interested in, or even arbitrary Go expressions, and see their values change as the program runs.<\/p>\n\n\n\n

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

JetBrains AI tools<\/h2>\n\n\n\n

You were expecting this, right? Everything has AI now (or as I like to say, \u201cEverything’s computer\u201d). GoLand’s optional AI Assistant plugin<\/a> is there, not to supplant your wonderfully human intelligence, but to support it.<\/p>\n\n\n\n

For example, you can highlight some code and ask the assistant to explain it,  suggest refactorings, or generate tests. You can ask it questions about the language or the standard library \u2013 all those \u201cat this point I’m afraid to ask\u201d things, and it won’t judge you.<\/p>\n\n\n\n

Naturally, you can also use Junie<\/a>, the JetBrains AI coding agent, as part of GoLand. You can ask Junie to write whole packages or programs for you, or to read a bunch of user requirements and sketch out a system design, then implement it.<\/p>\n\n\n\n

If there’s some project you’ve always wanted to write, but you aren’t sure how to get started, collaborating with Junie could get you unblocked. Think of Junie as a pair programmer who doesn’t get bored or lose focus, and who can help you out with program structure and algorithms while still letting you have the fun of writing the interesting parts yourself.<\/p>\n\n\n\n

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

There’s more<\/h2>\n\n\n\n

What’s that? Ten superpowers aren’t enough for you? You’ve got some attitude, mister. Look, GoLand can do more than we’ve had time to cover here \u2013 a lot<\/em> more. But these ten things are a great place to start. Once you’ve mastered them, feel free to explore: read the docs<\/a>, click around, try stuff out.<\/p>\n\n\n\n

Don’t be like my non-copy-pasting friend, always too busy cutting wood to stop and sharpen the saw. A few minutes a day invested in really learning your IDE is time well spent. Pretty soon, these superpowers will become part of your muscle memory, just like copy and paste. (GoLand has that too. You’re welcome.)<\/p>\n","protected":false},"author":1386,"featured_media":597304,"comment_status":"closed","ping_status":"closed","template":"","categories":[808],"tags":[],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/go\/596699"}],"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\/1386"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/comments?post=596699"}],"version-history":[{"count":10,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/go\/596699\/revisions"}],"predecessor-version":[{"id":603144,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/go\/596699\/revisions\/603144"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/media\/597304"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/media?parent=596699"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/categories?post=596699"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/tags?post=596699"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/zh-hans\/wp-json\/wp\/v2\/cross-post-tag?post=596699"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}