Skip to content

Exact func externtype types - #102

Open
tlively wants to merge 32 commits into
mainfrom
exact-extern-functype
Open

tlively wants to merge 32 commits into
mainfrom
exact-extern-functype

Conversation

@tlively

@tlively tlively commented Jul 8, 2026

Copy link
Copy Markdown
Member

Update the syntax of func externtypes and func types in the typing context to include exactness. This allows specifying exact function imports and properly typing ref.func as exact for exact imports and defined functions and otherwise as inexact.

tlively added 3 commits July 6, 2026 20:33
And struct.new_default_desc. Also update the valiation for struct.new and struct.new_default to require empty descriptors. Add an explanation of expansion to desctype to the validation conventions section and teach SpecTec about the new ExpandDesc relation to avoid errors during rendering.
Update the syntax of func externtypes and func types in the typing context to include exactness. This allows specifying exact function imports and properly typing ref.func as exact for exact imports and defined functions and otherwise as inexact.
@tlively
tlively requested a review from rossberg July 8, 2026 01:37
Comment thread document/core/util/macros.def Outdated
Comment on lines +93 to +96
def $exactheaptype(exact, typeuse) : heaptype

def $exactheaptype(EXACT, typeuse) = EXACT typeuse
def $exactheaptype(INEXACT, typeuse) = typeuse

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having the externtype and context store explicitly EXACT or INEXACT exactness instead of just containing an EXACT? is important for ensuring that both cases are handled everywhere. At the same time, it is annoying because heaptype has a different representation of exactness (... | typeuse | EXACT typeuse), so we require this auxiliary conversion function.

Do you have a recommendation for how to simplify this? I'm thinking that maybe we should be using heaptype instead of deftype/typeuse in the externtype and context definitions because heaptype already has exactness information built-in, and we would be able to avoid conversions that way. But then we might need a new form of expansion that can fish the type use out of both exact and inexact heap types instead :/

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I figured something out in #106

@tlively tlively mentioned this pull request Jul 9, 2026
4 of 51 tasks
tlively added 14 commits July 13, 2026 04:49
Previously the definition of `heaptype` was `... | EXACT typeuse | typeuse`, but this made it impossible to treat the exactness as a variable. Refactor the definition to `... | _HT exact? typeuse` instead. This is similar to how nullability is treated in reference types, except that the `_HT` tag will not be displayed in the rendered spec.
…nctype

Update the typing context to store heap types for functions.

@rossberg rossberg left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generalising the syntax of function types to arbitrary heaptypes is a bit nasty. Maybe we need an auxiliary form of type representing qualified type uses like exact? typeuse? Having a name and meta variable for that might also avoid the intrusive appearance of the _HT constructor everywhere, like in the other PR.

@tlively

tlively commented Jul 24, 2026

Copy link
Copy Markdown
Member Author

Oh interesting, I used to have an exacttypeuse production similar to what you're describing, but then I switched to using heaptype because it seemed simpler. I can play around with it more, though.

# Conflicts:
#	specification/wasm-latest/1.2-syntax.types.spectec
#	specification/wasm-latest/1.3-syntax.instructions.spectec
#	spectec/src/backend-prose/gen.ml
#	spectec/test-frontend/TEST.md
…nctype

# Conflicts:
#	document/core/valid/conventions.rst
#	specification/wasm-latest/1.2-syntax.types.spectec
#	specification/wasm-latest/2.4-validation.modules.spectec
#	spectec/test-frontend/TEST.md
Base automatically changed from struct-new-desc-syntax-validation to main October 14, 2026 14:34
@tlively tlively changed the title Exact func externtypes types Exact func externtype types Oct 15, 2026
@tlively

tlively commented Oct 15, 2026

Copy link
Copy Markdown
Member Author

@rossberg, I updated the approach here to match your suggestion in #102 (review). This is ready for another look.

@tlively
tlively requested a review from rossberg October 15, 2026 03:09
Comment on lines +131 to +132
C |- FUNC x : FUNC exact? dt
-- if C.FUNCS[x] = exact? dt

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
C |- FUNC x : FUNC exact? dt
-- if C.FUNCS[x] = exact? dt
C |- FUNC x : FUNC edt
-- if C.FUNCS[x] = edt

----
-- if C' = {TYPES dt'*, GLOBALS gt_I*, FUNCS dt_I* dt*, REFS x*}
-- if C' = {TYPES dt'*, GLOBALS gt_I*, FUNCS edt_I* edt*, REFS x*}
-- if edt* = (EXACT dt)*

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be appropriate if Func_ok itself returned the edt now, since that's what functions are classified with.

(Nice side effect: you can rename dt' to plain dt.)

MEMS memtype*,
TABLES tabletype*,
FUNCS deftype_F*,
FUNCS edt_F*,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency:

Suggested change
FUNCS edt_F*,
FUNCS exactdeftype*,

Comment on lines +183 to +184
-- (Externaddr_ok: s |- FUNC funcaddr : FUNC exact? dt_F)*
-- if edt_F* = (exact? dt_F)*

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
-- (Externaddr_ok: s |- FUNC funcaddr : FUNC exact? dt_F)*
-- if edt_F* = (exact? dt_F)*
-- (Externaddr_ok: s |- FUNC funcaddr : FUNC exactdeftype)*

\CMEMS & \memtype^\ast, \\
\CTABLES & \tabletype^\ast, \\
\CFUNCS & {\deftype'}^\ast, \\
\CFUNCS & (\exact^?~\deftype')^\ast, \\

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
\CFUNCS & (\exact^?~\deftype')^\ast, \\
\CFUNCS & \exactdeftype^\ast, \\

C |- FUNC deftype_1 <: FUNC deftype_2
-- Deftype_sub: C |- deftype_1 <: deftype_2
C |- FUNC exact_1? deftype_1 <: FUNC exact_2? deftype_2
-- Heaptype_sub: C |- (_HT exact_1? deftype_1) <: (_HT exact_2? deftype_2)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
-- Heaptype_sub: C |- (_HT exact_1? deftype_1) <: (_HT exact_2? deftype_2)
-- Heaptype_sub: C |- _HT exact_1? deftype_1 <: _HT exact_2? deftype_2

syntax deftype hint(desc "defined type") =
| _DEF rectype n hint(show %.%)

syntax exactdeftype hint(desc "function type") hint(show (exact? deftype)) = exact? deftype

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, this show hint is rather hacky, it won't work correctly if somebody needs to use something like exactdeftype_i anywhere. I see that you avoid that by always expanding it out, but it would probably be cleaner if we introduced exactdeftype properly as a new type form.

MEMS mt*,
TABLES tt*,
FUNCS dt_F*,
FUNCS edt_F*,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
FUNCS edt_F*,
FUNCS edt*,

-- (Globaltype_ok: C_0 |- gt : OK)*
-- (Memtype_ok: C_0 |- mt : OK)*
-- (Tabletype_ok: C_0 |- tt : OK)*
-- if edt_F* = (exact? dt_F)*

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
-- if edt_F* = (exact? dt_F)*
-- if edt* = (exact? dt_F)*

-- (Resulttype_ok: C_0 |- t*: OK)*
-- (Resulttype_ok: C_0 |- t'* : OK)?
-- (if x < |dt_F*|)*
-- (if x < |edt_F*|)*

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
-- (if x < |edt_F*|)*
-- (if x < |edt*|)*

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants