From e75ef5e1337a0204e7bfb8c145efb2e646a11c92 Mon Sep 17 00:00:00 2001 From: Akuli Date: Tue, 14 Jan 2025 00:34:49 +0200 Subject: [PATCH] fix link :) --- doc/imports.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/imports.md b/doc/imports.md index f89a1977..c1a046a3 100644 --- a/doc/imports.md +++ b/doc/imports.md @@ -92,5 +92,5 @@ a Jou function named `foo()` is actually named `foo()`. Methods are entirely a Jou concept, and they become plain old functions when the Jou code is compiled. If you have a Jou method `bark()` in Jou class `Dog`, the compiler generates a function named `Dog.bark`. -This means that debugging tools (e.g. [valgrind](doc.md#crashing-and-valgrind)) +This means that debugging tools (e.g. [valgrind](doc/ub.md#crashing-and-valgrind)) show `Dog.bark` as the function name when they tell you something about the Jou method.