Skip to content

[Docs] Follow TileOPs manifest argument types, merged ops and the vLLM RoPE family - #86

Merged
lcy-seso merged 1 commit into
tile-ai:mainfrom
lcy-seso:docs/argument-types
Nov 16, 2026
Merged

lcy-seso merged 1 commit into
tile-ai:mainfrom
lcy-seso:docs/argument-types

Conversation

@lcy-seso

@lcy-seso lcy-seso commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

Follows tile-ai/TileOPs#2958; merge after it.

Changes

  • Manifest pages describe call-time type/default, member(), list[Tensor] and random_ints.
  • API and user-guide pages name ClampFwdOp, LerpFwdOp and MaskedFillFwdOp in place of the Scalar/Tensor pairs.
  • RoPE pages follow the vLLM (positions, query, key) signature; RoPENeoxPositionIdsFwdOp is gone.

…M RoPE family

TileOPs now declares a call-time input's argument type and default instead of
`optional`, keeps every tensor a call-time input, and accepts tensor sequences.
The manifest guide, the op guide, the backend guide and their figures still
described `optional`, `.value` and construction-time tensors, so readers would
write specs the validator rejects.

The guide now covers argument members, member(), call-time scalars, operator
slots and tensor sequences, in English and Chinese alike. The API pages list
ClampFwdOp, LerpFwdOp and MaskedFillFwdOp in place of their scalar and tensor
halves and drop RoPENeoxPositionIdsFwdOp, whose job RoPEFwdOp(is_neox_style=True)
now does.

The benchmark renderer reads a row's call-time scalars, shows them beside the
parameters, expands tensor sequences per element and shortens float lists such
as LongRoPE's rescale_factors.
@lcy-seso
lcy-seso merged commit 97a3a53 into tile-ai:main Nov 16, 2026
5 of 6 checks passed
lcy-seso added a commit that referenced this pull request Nov 16, 2026
… reviewed 0.x breaks (#87)

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.
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