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

No integer/float subtype: integral floats print as integers, next(t, k) with float k computed at runtime continues (#42 literal-only)

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
lua
Domain
compilers

Research direction

Start with GAPS.md, which does not yet declare this gap, and with the three Lua snippets in the issue body, which show the reference output against EigenLua's current output. The next(t, k) float-key check lives on the fix-small-4 branch and only matches float literals passed at the call site. Done means either the runtime carries an integer/float subtype so the three snippets match as a Tier D row, or GAPS.md lists the consequences (integral-float printing, // and % by zero, the next cursor quirk, math.type).

Written by the indexing model from the issue text.

Description

bug eigenscript-gap

Found by the blind critic for fix-small-4 (#40/#42/#44/#45). Reproduces on origin/main 9536f4c.

EigenLua has no integer/float subtype at runtime: every Lua number becomes an EigenScript num. Several reference behaviours depend on the subtype:

print(1.0, "10.0"+1, math.type("10.0"+1))   -- ref: 1.0  11.0  float
print("1.0" // "0")                         -- ref: inf
local t = {}; t[1] = "one"; t[2.0] = "two"
local k = 1.0
print(pcall(next, t, k))                    -- ref: false  invalid key to 'next'

eigenlua: 1 11 integer, attempt to divide by zero, true 2 two.

The fix-small-4 branch makes next(t, 1.0) match only when a float literal is passed to next(...) or pcall(next, ...), using call-site metadata. A float that is computed, stored in a variable or table, passed through a vararg or select, or sent through coroutine.wrap(next) / pcall(pcall, next, ...) still continues instead of raising. Existing D rows that diverge for this reason: int_one_vs_one, str_format_num, ops_matrix (u- gives -0 float), and others.

GAPS.md does not declare this gap.

Done when

Either the runtime carries the subtype, so that the three lines above MATCH as a Tier D row, or GAPS.md declares the gap and lists the observable consequences (integral-float printing, // and % by zero, the next cursor quirk, math.type).

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.