Skip to content

Add Elixir-specific note to Hamming instructions#1647

Open
tolbier wants to merge 1 commit into
exercism:mainfrom
tolbier:hamming-add-approach-note
Open

Add Elixir-specific note to Hamming instructions#1647
tolbier wants to merge 1 commit into
exercism:mainfrom
tolbier:hamming-add-approach-note

Conversation

@tolbier

@tolbier tolbier commented Jul 22, 2026

Copy link
Copy Markdown

Summary

  • Adds an instructions.append.md for the Hamming exercise clarifying that it's intended to reinforce Enum usage, while noting it can also be solved with other methods.

Motivation

While solving this exercise, I started with an Enum-based approach and later rewrote it using recursion/pattern matching, realizing the exercise's intent (practicing Enum) wasn't explicit anywhere in the instructions.

Test plan

  • N/A (docs-only change)

Clarify that the exercise is meant to reinforce Enum usage, while
noting it can also be solved with other methods.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Thank you for contributing to exercism/elixir 💜 🎉. This is an automated PR comment 🤖 for the maintainers of this repository that helps with the PR review process. You can safely ignore it and wait for a maintainer to review your changes.

Based on the files changed in this PR, it would be good to pay attention to the following details when reviewing the PR:

  • General steps

    • 🏆 Does this PR need to receive a label with a reputation modifier (x:size/{tiny,small,medium,large,massive})? (A medium reputation amount is awarded by default, see docs)
  • Any exercise changed

    • 👤 Does the author of the PR need to be added as an author or contributor in <exercise>/.meta/config.json (see docs)?
    • 🔬 Do the analyzer and the analyzer comments exist for this exercise? Do they need to be changed?
    • 📜 Does the design file (<exercise>/.meta/design.md) need to be updated to document new implementation decisions?
  • Practice exercise changed

    • 🌲 Do prerequisites, practices, and difficulty in config.json need to be updated?
    • 🧑‍🏫 Are the changes in accordance with the community-wide problem specifiations?

Automated comment created by PR Commenter 🤖.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant