Skip to content

Redefine / clarify purpose of examples #73

Open
@camstuart

Description

See also @Altai-man's comment: #57 (comment)

The examples directory requires attention. I am in the process of bringing file extensions (see also #72) and shebangs inline with current Raku conventions. But further attention is required to tidy up these examples, and repair publishing.

At a high level, my view is the Raku/examples directory should:

  • Make it easy for users to find (and execute) examples
  • have a "real world" nature wherever possible, including some explanatory text
  • Offer the community a place to contribute their valuable examples for others to benefit from
  • Have strong ties (bi-directional links to) official Raku documentation (IE, see example and follow link to reference docs, or see reference docs and follow link back to examples)

Commencing with the cookbook:

I propose further cookbook style recipes that offer typical programming activities and how they might be solved in Raku. Including multi paradigm examples, and alternative approaches to achieve the same result to ensure the TIMTOWTDI mindset can continue to prosper.

Currently, the Raku/examples/cookbook is a "tip of the hat" back to the excellent Perl Cookbook.

This is fantastic for Perl 5's posterity and certainly something we should continue maintain, however it fails to showcase Raku's capabilities that make it a more modern language. For one example, concurrency. One area among others that most certainly should have multiple cookbook recipes.

TODO:

Continue to maintain and enhance the existing cookbook examples:

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions