From 2534eea023492efbbe66bc2a22d50c35192f9d40 Mon Sep 17 00:00:00 2001 From: Quentin Bernet Date: Tue, 4 Apr 2023 14:30:46 +0200 Subject: [PATCH 1/2] Add links to debugger in inspection article Makes the new debugger article more visible by linking from a page that benefits from it, "How to Inspect Values" --- _overviews/scala3-contribution/procedures-inspection.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/_overviews/scala3-contribution/procedures-inspection.md b/_overviews/scala3-contribution/procedures-inspection.md index 6876882e41..a2577f2f8c 100644 --- a/_overviews/scala3-contribution/procedures-inspection.md +++ b/_overviews/scala3-contribution/procedures-inspection.md @@ -13,7 +13,9 @@ while the compiler is running, and inspect produced artifacts of the compiler. ## Inspecting variables in-place Frequently you will need to inspect the content of a particular variable. -Often, it is sufficient to use `println`. +You can either use `println`s or the debugger, more info on how to setup the latter [here](https://docs.scala-lang.org/scala3/guides/contribution/procedures-debugging.html). + +In the remeainder of this article we'll use `println()` inserted in the code, but the same effect can be accomplished by stopping at a breakpoint, and typing `` in the [debug console](https://docs.scala-lang.org/scala3/guides/contribution/procedures-debugging.html#the-debug-console) of the debugger. When printing a variable, it's always a good idea to call `show` on that variable: `println(x.show)`. Many objects of the compiler define `show`, returning a human-readable string. From 7b1f1e454e833dd3ae105bb515075e19894f0188 Mon Sep 17 00:00:00 2001 From: Julien Richard-Foy Date: Wed, 12 Apr 2023 14:23:33 +0200 Subject: [PATCH 2/2] Apply suggestions from code review --- _overviews/scala3-contribution/procedures-inspection.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_overviews/scala3-contribution/procedures-inspection.md b/_overviews/scala3-contribution/procedures-inspection.md index a2577f2f8c..891f3ee5eb 100644 --- a/_overviews/scala3-contribution/procedures-inspection.md +++ b/_overviews/scala3-contribution/procedures-inspection.md @@ -13,9 +13,9 @@ while the compiler is running, and inspect produced artifacts of the compiler. ## Inspecting variables in-place Frequently you will need to inspect the content of a particular variable. -You can either use `println`s or the debugger, more info on how to setup the latter [here](https://docs.scala-lang.org/scala3/guides/contribution/procedures-debugging.html). +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 %}). -In the remeainder of this article we'll use `println()` inserted in the code, but the same effect can be accomplished by stopping at a breakpoint, and typing `` in the [debug console](https://docs.scala-lang.org/scala3/guides/contribution/procedures-debugging.html#the-debug-console) of the debugger. +In the remeainder of this article we'll use `println()` inserted in the code, but the same effect can be accomplished by stopping at a breakpoint, and typing `` in the [debug console]({% link _overviews/scala3-contribution/procedures-debugging.md %}#the-debug-console) of the debugger. When printing a variable, it's always a good idea to call `show` on that variable: `println(x.show)`. Many objects of the compiler define `show`, returning a human-readable string.