jwalsh/hy-algorithms

Create comprehensive algorithm cheat sheets

Open

#47 opened on Mar 29, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Hy (0 forks)auto 404
documentationgood first issue

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (PR metrics pending)

Description

Develop comprehensive algorithm cheat sheets for quick reference:

Cheat sheet categories:

  • Sorting algorithms
  • Searching algorithms
  • Graph algorithms
  • Dynamic programming patterns
  • Tree algorithms
  • String algorithms
  • Mathematical algorithms

Content for each algorithm:

  • Time and space complexity
  • Key characteristics
  • When to use / when not to use
  • Implementation hints
  • Common pitfalls
  • Code snippet in Hy

Format options:

  • Markdown documentation
  • Printable PDF
  • Interactive web version
  • Comparison tables

Additional features:

  • Decision flowcharts for algorithm selection
  • Visual algorithm comparison
  • Problem-to-algorithm mapping guide
  • Quick implementation templates

These cheat sheets will serve as quick references for algorithm selection and implementation, helping users choose the right algorithm for specific problems and remember key implementation details.

Contributor guide

Research direction
Familiarize yourself with the Hy language and the repository's existing algorithm implementations. Choose one algorithm category (e.g., sorting) and study common algorithms. Document time/space complexity, key characteristics, when to use/avoid, implementation hints, common pitfalls, and a Hy code example. Follow the repository's documentation style and consider starting with Markdown format.
Tech stack
None
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitHy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75