tarantool / tarantool/checks

Exclude `nil` function name from error

Open
#61 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
20
Forks
4
PR merge metrics
No merged PRs in 30d

Description

local function f(_)
	require("checks")("number")
end

assert(pcall(f, ""))
-- bad argument #1 to nil (number expected, got string)

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by running the Lua reproduction from issue #61 and trace how checks builds the argument error when the function name is nil. Done means the failing call no longer includes "nil" in the error message while the type-checking failure remains clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.