From 9c17f5cb60284191a831a95703545c084b449a0f Mon Sep 17 00:00:00 2001 From: Dan King Date: Mon, 6 Apr 2026 11:25:30 -0400 Subject: [PATCH] fix: RFC-0029 consistently use "Array" rather than "Encoding" `s` cannot be a right inverse of $\pi$ unless its output type is the input type of $\pi$. Signed-off-by: Dan King --- proposed/0029-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposed/0029-types.md b/proposed/0029-types.md index 68b0b57..cda5533 100644 --- a/proposed/0029-types.md +++ b/proposed/0029-types.md @@ -128,7 +128,7 @@ Observe that every physical array (a specific encoding combined with actual data array. A `VarBinView` array can map to either `Utf8` or `Binary`, depending on whether its contents are valid UTF-8. Call this projection `π : Array → DType`. -A **section** is a right-inverse of this projection: a function `s : DType → Encoding` that injects +A **section** is a right-inverse of this projection: a function `s : DType → Array` that injects each logical type back into the space of physical encodings, such that projecting back recovers the original `DType` (`π(s(d)) = d`). In other words, a section answers the question: "given a logical type, which physical encoding should I use to represent it?"