@jutge.org/toolkit 4.4.45 → 4.4.48

package/assets/prompts/io/creators/create-solution.tpl.txt

@@ -10,6 +10,8 @@ Take these instructions into account:
 
 - The code must be well written and easy to understand to novices. It cannot use advanced constructs.
 
+- Never overoptimize.
+
 - The code does not have to check the preconditions stated in the problem statement.
 
 - Do not use any non-standard libraries.

package/assets/prompts/io/proglangs/cc.md

@@ -4,4 +4,6 @@
 
 - Add a `using namespace std;` declaration after the include section and do not use `std::` prefixes.
 
-- Avoid the use of long long ints and use ints instead.
+- Avoid the use of `long long int` and use `int` instead.
+
+- Avoid using `break`, `continue` and exceptions.

package/assets/prompts/io/proglangs/py.md

@@ -4,6 +4,10 @@
 
 - Use type hints for function definitions. Do not use old-style type hints such as `List[int]` with `List` imported from `typing`, but use modern syntax such as `list[int]`.
 
+- Use `type` keyword or `TypeAlias` with a suitable semantic name rather than repeating raw complex types. For instance, use `type Temperatures = list[float]` instead of `list[float]`.
+
+- Avoid using `break`, `continue` and exceptions.
+
 - Ensure that the generated Python3 code follows best practices, including proper indentation, use of functions, use of docstrings, and adherence to PEP 8 style guidelines.
 
 # Very important
@@ -41,4 +45,6 @@ for x in tokens(int):  # iterates over all integers in the input
 print(s) # prints the sum of all the integers in the input
 ```
 
+Priorize `tokens(type)` over `scan(type)` when possible.
+
 In yogi functions, `type` can be `int`, `float`, or `str`.