Bug in positional only arguments separator '/'

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, python
Domain
compilers

Research direction

Run the provided Python snippet through Transcrypt and compare the generated JavaScript with the issue's output. Trace how the compiler handles the positional-only separator / and argument binding. Done means the generated code binds s when Q(3) is called without producing the reported error.

Written by the indexing model from the issue text.

Description

IS: enhancement STATE: under consideration 
def Q(s, /):
    print(s)

Q(3)

is translated as

export var Q=function(){__call__(print,null,s)}
__call__(Q,null,3)

which generates an error because s is not bound to anything.

Dominant language
Python
Stars
2.9k
Forks
218
No merged PRs in 30d

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.

More from TranscryptOrg/Transcrypt

All issues in TranscryptOrg/Transcrypt

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.