From a32ac2097cf482d44ea2bb4c18d5cb982206434f Mon Sep 17 00:00:00 2001 From: Isaac Good Date: Mon, 25 May 2026 15:09:31 -0700 Subject: [PATCH] Format all `instructions.append.md` to start with an H1 (required but ignored) and H2 --- exercises/practice/anagram/.docs/instructions.append.md | 2 ++ .../practice/bank-account/.docs/instructions.append.md | 2 ++ exercises/practice/clock/.docs/instructions.append.md | 2 ++ .../practice/flatten-array/.docs/instructions.append.md | 2 ++ .../practice/high-scores/.docs/instructions.append.md | 7 ++++++- 5 files changed, 14 insertions(+), 1 deletion(-) diff --git a/exercises/practice/anagram/.docs/instructions.append.md b/exercises/practice/anagram/.docs/instructions.append.md index 2b17bb7a..0f5c35b6 100644 --- a/exercises/practice/anagram/.docs/instructions.append.md +++ b/exercises/practice/anagram/.docs/instructions.append.md @@ -1,3 +1,5 @@ # Instructions Append +## Implementation + You must return the anagrams in the same order as they are listed in the candidate words. diff --git a/exercises/practice/bank-account/.docs/instructions.append.md b/exercises/practice/bank-account/.docs/instructions.append.md index 78702bb1..78f560f5 100644 --- a/exercises/practice/bank-account/.docs/instructions.append.md +++ b/exercises/practice/bank-account/.docs/instructions.append.md @@ -1,3 +1,5 @@ # Instructions append +## Implementation + Pyret doesn't support concurrency so that requirement can be set aside. Account operations are sequential on a single thread. diff --git a/exercises/practice/clock/.docs/instructions.append.md b/exercises/practice/clock/.docs/instructions.append.md index 051babd0..860f7977 100644 --- a/exercises/practice/clock/.docs/instructions.append.md +++ b/exercises/practice/clock/.docs/instructions.append.md @@ -1,5 +1,7 @@ # Instructions append +## Implementation + The tests for this exercise expect that your clock will be implemented using a `data declaration` in Pyret. If you are unfamiliar with data declarations, [the official documentation][data-declaration] is a good place to start. diff --git a/exercises/practice/flatten-array/.docs/instructions.append.md b/exercises/practice/flatten-array/.docs/instructions.append.md index 01209f69..dcb47e53 100644 --- a/exercises/practice/flatten-array/.docs/instructions.append.md +++ b/exercises/practice/flatten-array/.docs/instructions.append.md @@ -1,5 +1,7 @@ # Instructions append +## Implementation + This exercise is implemented using the built-in [List] datatype, not RawArrays. [list]: https://pyret.org/docs/latest/lists.html diff --git a/exercises/practice/high-scores/.docs/instructions.append.md b/exercises/practice/high-scores/.docs/instructions.append.md index 3dece387..f5670c35 100644 --- a/exercises/practice/high-scores/.docs/instructions.append.md +++ b/exercises/practice/high-scores/.docs/instructions.append.md @@ -1,6 +1,11 @@ # Instructions append -Many of our lower-level Pyret exercises are solveable with only [function application expressions] in the form of `foo(1)` . This exercise however expects that [dot expressions] can be used to access data and method fields on what your function returns. This can be done with [object expressions], allowing you to access the fields of an object literal. [Data declarations] are a similar but more advanced approach that utilizes data and method fields as well. +## Implementation + +Many of our lower-level Pyret exercises are solveable with only [function application expressions] in the form of `foo(1)` . +This exercise however expects that [dot expressions] can be used to access data and method fields on what your function returns. +This can be done with [object expressions], allowing you to access the fields of an object literal. +[Data declarations] are a similar but more advanced approach that utilizes data and method fields as well. [function application expressions]: https://pyret.org/docs/latest/Expressions.html#%28part._s~3aapp-expr%29 [dot expressions]: https://pyret.org/docs/latest/Expressions.html#%28part._s~3adot-expr%29