Skip to content

[Docs] Follow TileOPs: validate_inputs bounds, int for float members, reviewed 0.x breaks - #87

Merged
lcy-seso merged 2 commits into
tile-ai:mainfrom
lcy-seso:docs/argument-types-followup
Nov 16, 2026
Merged

lcy-seso merged 2 commits into
tile-ai:mainfrom
lcy-seso:docs/argument-types-followup

Conversation

@lcy-seso

Copy link
Copy Markdown
Contributor

Follows tile-ai/TileOPs#2958 (squash commit 0b1063ad8), after #86 tracked it up to an earlier commit.

Problems

  • The manifest pages, the call steps, the op lifecycle table and the new-op guide say validate_inputs checks only packed offsets; TileOPs now also checks every in_range bound, and an op without packed offsets may declare the flag for its bounds alone.
  • The extensions page says an int takes only an int or Number member; TileOPs now lets it take a float member when neither exists.
  • The extensions page says any Maybe discriminant matches by value; TileOPs restricts that to Maybe[ADT].
  • The Chinese stability page still says 0.x minor releases change the public API only additively; TileOPs now allows a reviewed break in a minor release, listed in the release notes and scripts/ci/api_compat_allow.txt.

Changes

  • user-guide/manifest/extensions: the validate_inputs rule covers prefix_offsets and in_range, and other predicates stay the caller's obligation.
  • user-guide/manifest/extensions: the float member row and the member rule accept an int when no int or Number member takes it.
  • user-guide/manifest/extensions: the type family rule names Maybe[ADT].
  • user-guide/manifest/calls, user-guide/op/lifecycle, new-op: the validate_inputs step names in_range bounds.
  • stability.zh: the compatibility section matches the mirrored English page.
  • Each change is made to the English page and its .zh.md pair; the design pages, the English stability page and the API pages follow TileOPs at build time and need no edit.

… reviewed 0.x breaks

TileOPs now checks every `in_range` bound of an op's inputs under
`validate_inputs`, not only packed offsets, and an op without packed offsets
may declare the flag for its bounds alone. The manifest pages, the call steps,
the op lifecycle table and the new-op guide said the check covered packed
offsets only.

An `int` now takes a `float` member when no `int` or `Number` member does, and
only a `Maybe[ADT]` is a discriminant that a type family matches by value. The
extensions page still stated the earlier rules.

The stability page is mirrored in English, but its Chinese page is written by
hand, so it is updated to the new compatibility rule: a 0.x minor release may
carry a reviewed break, listed in the release notes and in
`scripts/ci/api_compat_allow.txt`.
@lcy-seso
lcy-seso merged commit 10c4fa5 into tile-ai:main Nov 16, 2026
3 checks passed
@lcy-seso
lcy-seso deleted the docs/argument-types-followup branch November 16, 2026 03:42
lcy-seso added a commit that referenced this pull request Nov 18, 2026
…p the mHC ops (#88)

Follows tile-ai/TileOPs#3021 and the ops TileOPs main added since #87.

## Problems

- Six ops TileOPs exports have no API page: `EmbeddingFwdOp`,
`ConcatFwdOp`, `MaskedScatterFwdOp` (the new `tileops.indexing` family),
`RMSNormGatedFwdOp`, `MoEGroupedGEMMMXFP4FwdOp` and `RoPECosSinFwdOp`.
- tile-ai/TileOPs#3021 removes `MHCPreFwdOp` and `MHCPostFwdOp`; once it
merges, the mHC page names ops the build cannot collect.

## Changes

- New `api/indexing` page for the three indexing ops, in the nav after
Transform.
- `RMSNormGatedFwdOp` on Normalization, `MoEGroupedGEMMMXFP4FwdOp` on
MoE beside the FP8 grouped GEMM, and `RoPECosSinFwdOp` in a new RoPE
section.
- Remove the mHC page, its nav and translation entries, and the `mhc`
family of the Benchmarks generator.
- Drop the `mhc.expansion` example from the manifest calls page (English
and Chinese); no other spec uses that primitive.
- `scripts/check_api_pages.py` against tile-ai/TileOPs#3021: 209 ops,
all on a page. Against current main it passes and lists only the two mHC
ops as unnamed.
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.

1 participant