Skip to content

fix: RFC-0029 consistently use "Array" rather than "Encoding" #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
connortsui20 merged 1 commit into from
Apr 6, 2026
+1 −1
Merged

fix: RFC-0029 consistently use "Array" rather than "Encoding" #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion proposed/0029-types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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?"
Expand Down
Loading