Skip to content

Commit d66d766

Browse files
authored
Add links to debugger in inspection article (#2762)
1 parent b26b7c5 commit d66d766

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

_overviews/scala3-contribution/procedures-inspection.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,9 @@ while the compiler is running, and inspect produced artifacts of the compiler.
1313
## Inspecting variables in-place
1414

1515
Frequently you will need to inspect the content of a particular variable.
16-
Often, it is sufficient to use `println`.
16+
You can either use `println`s or the debugger, more info on how to setup the latter [here]({% link _overviews/scala3-contribution/procedures-debugging.md %}).
17+
18+
In the remeainder of this article we'll use `println(<someUsefulExpression>)` inserted in the code, but the same effect can be accomplished by stopping at a breakpoint, and typing `<someUsefulExpression>` in the [debug console]({% link _overviews/scala3-contribution/procedures-debugging.md %}#the-debug-console) of the debugger.
1719

1820
When printing a variable, it's always a good idea to call `show` on that variable: `println(x.show)`.
1921
Many objects of the compiler define `show`, returning a human-readable string.

0 commit comments

Comments
 (0)