Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Tier D: cover utf8.codes / utf8.offset edge cases

Open
  • Is something wrong?
#61 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
66/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
lua
Domain
testing

Research direction

Start by reading an existing Tier D program under corpus/D/ to match its style, then look at how tools/grade.sh runs and diffs output against reference Lua 5.4.9. Write corpus/D/utf8_codes_offset.lua covering the listed utf8.offset and utf8.codes edges, and run tools/grade.sh --tier D --only utf8_codes_offset. Done means it MATCHes, or each divergence is recorded in LEDGER.md, and bash tests/run.sh passes.

Written by the indexing model from the issue text.

Description

front-end good first issue

utf8.codes and utf8.offset each appear in only one Tier D program. Add a small corpus/D/utf8_codes_offset.lua that exercises their edges. The grader diffs it against reference Lua 5.4.9, so there's no expected output to write.

Suggested edges:

  • negative and out-of-range i for utf8.offset;
  • n = 0;
  • continuation-byte starts;
  • invalid sequences under utf8.codes, wrapped in pcall to print the error;
  • the lax argument.

If a line diverges because of an EigenScript limitation (for example NUL bytes in strings), record it in LEDGER.md rather than changing the program to avoid it.

Done when

  • corpus/D/utf8_codes_offset.lua exists and MATCHes the reference under tools/grade.sh --tier D --only utf8_codes_offset, or every divergence is classified in LEDGER.md.
  • bash tests/run.sh passes.
Dominant language
Lua
Stars
0
Forks
0
Avg merge
54m
Merged PRs (30d)
19

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from InauguralSystems/EigenLua

All issues in InauguralSystems/EigenLua

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.