Consistent parameter order between cont.bind and switch tags

Open

#67 opened on Jul 30, 2024 23 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 35/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: wasm
Domain: compilers

Research direction

Start with the explainer's rules for cont.bind and switch-tag parameter ordering, then read the referenced discussion on pull request #66 for the compatibility context. Done means the chosen cont.bind order and switch-tag continuation parameter position are consistent while preserving the described usage patterns.

Written by the indexing model from the issue text.

Description

The explainer currently proposes to change the order in which cont.bind binds arguments. However, it needs to remain possible to use cont.bind to supply the (regular) arguments to a continuation used with switch, otherwise certain usage patterns that use cont.bind to unify continuation argument types would break (see comment for some context).

If we keep the changed order of cont.bind, we hence need to consistently change the position of the continuation parameter to a switch tag from last to first:

   - and `C.types[$ct1] ~~ cont $ft1`
   - and `C.types[$ft1] ~~ [(ref null? $ct2) t1*] -> [te1*]`

Dominant language: WebAssembly
Stars: 216
Forks: 19
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

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

Similar issues

isolated-declarations: TS9025 on an optional parameter property typed `readonly T[]`, which tsc 7 accepts Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

oxc-project/oxc#26944 · Opened Sep 22, 2026
perf: a definite-value return type (`--> Nil`, `--> True`) sends every call down the full path (~12 µs vs ~1 µs) Open

todo:perf

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

tokuhirom/mutsu#9074 · Opened Sep 22, 2026
A function-call exponent (`A^sqrt(n)`) emits `pow(A, sqrt)(n)` — valid BNGL that codegen cannot compile Open

bug

Difficulty 2/5 Half a day Newbie friendliness 82/100

lanl/bngsim#657 · Opened Sep 22, 2026
tt_metal/hw/inc/internal/tt-2xx/quasar/overlay/xcustom_test.hpp needs reimplementing Open

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

tenstorrent/tt-metal#57393 · 1 comment · Opened Sep 22, 2026
StUnhex.number() misformats Long.MIN_VALUE as scientific notation instead of a plain integer Open

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

objectionary/eo#8894 · Opened Sep 22, 2026

More Compilers issues