Operations

Which namespace an operator lives in, how to choose between them, and what the operator surface contains.

Prerequisites: Types.

What this chapter is

Two pages, deliberately thin:

Page	What it covers
Choosing a Namespace	The rule for picking pl.* versus pl.tensor.* versus pl.tile.*, and when the unified form cannot be used
Catalog	Every operator family, one line each, with the namespace it is reachable from

Signatures are not duplicated here. Nearly every operator in pl.__all__ carries a docstring, and that docstring is the reference — a hand-maintained signature table would drift from it within a release. The API Reference renders those docstrings, and every name in the catalog links straight into it. So the catalog answers "what is there, and what is it called"; the API reference answers "what are its arguments".

For "how do I use this operator to do something useful", the answer is a worked example, not a table — see Tutorials, or examples/beginner/ and examples/intermediate/ in the repository.

See Also

• Language Guide — the constructs these operators appear inside.
• Memory and Data Movement — the movement operators in context.
• IR Operators — the operator registry these names resolve to.
• PTOAS Operator Status — backend support per operator.