Skip to content

[cluster] Less unsafe in row decoding / frontegg#35035

Draft
bkirwi wants to merge 2 commits intoMaterializeInc:mainfrom
bkirwi:less-unsafe
Draft

[cluster] Less unsafe in row decoding / frontegg#35035
bkirwi wants to merge 2 commits intoMaterializeInc:mainfrom
bkirwi:less-unsafe

Conversation

@bkirwi
Copy link
Contributor

@bkirwi bkirwi commented Feb 16, 2026

No description provided.

This was the only use of the safety invariant in row decoding, which
means that we no longer need `unsafe` annotations on functions that
create rows from byte arrays.
@github-actions
Copy link

Pre-merge checklist

  • The PR title is descriptive and will make sense in the git log.
  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).

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