Raku Resolutions #3: Addressing Language Design and Core Repository Deficits

Raku Resolutions #3

Elizabeth Mattijsen hosted the third Raku Resolutions meeting on February 21, 2026, involving three Steering Council members. The group addressed seven distinct technical issues within a strict one-hour time limit.

Why This Matters

The gap between language design ideals and the reality of core maintenance is highlighted by the unresolvable status of the Rakudo issue deficit, where the current team size cannot keep pace with new incoming issues. This meeting demonstrates the necessity of prioritizing pragmatic fixes, such as the :no-backtrace argument for die(), over theoretical perfection in order to manage limited developer resources effectively.

Key Insights

The Steering Council agreed that unit scope should logically apply to the entire source regardless of its position in the code, a change to be documented for future implementation (2026).
Raku’s List element indexing will maintain consistency by returning Nil for out-of-bounds access and Failure for negative indices, matching Array behavior.
The Rakudo repository’s issue deficit was declared unresolvable due to a fixed core team size and a continuous influx of new reports (2026).
New language features like :no-backtrace for die() were implemented in PR #6076 to replace the non-catchable note $message; exit 1 pattern.
Math and statistics functions will remain in module land rather than being integrated into the core language to maintain a lean core.

Practical Applications

Use Case: Implementing end-user error messages using die($msg, :no-backtrace) allows for clean output while remaining catchable by CATCH blocks. Pitfall: Using exit 1 directly prevents error recovery and structured exception handling.
Use Case: Organizing community resources under the new raku.org site to prevent stale documentation. Pitfall: Maintaining separate community pages can lead to fragmented information and outdated links.

References:

On This Page