#2 Use per-entity ID type

닫힘
kestrel3 년 전을 오픈 · 0개의 코멘트
kestrel 코멘트됨, 3 년 전

Rather than the current universal query::ID rowid wrapper, ideally we want an entirely separate type so that the compiler can help with accidental cross-table ID use.

The problem with this is mostly the column names of serialized structs (especially newtype structs) are not currently clear, and if there are multiple (e.g. for a struct S (i64, i64)) then it's not clear to the derive macro exactly how many table columns there are.

This may mean that we are limited to newtype structs and tuples, as tuples should be handlable with a .i suffix.

Rather than the current universal `query::ID` rowid wrapper, ideally we want an entirely separate type so that the compiler can help with accidental cross-table ID use. The problem with this is mostly the column names of serialized structs (especially newtype structs) are not currently clear, and if there are multiple (e.g. for a `struct S (i64, i64)`) then it's not clear to the derive macro exactly how many table columns there are. This may mean that we are limited to newtype structs and tuples, as tuples should be handlable with a `.i` suffix.
로그인하여 이 대화에 참여
레이블 없음
마일스톤 없음
담당자 없음
참여자 1명
로딩중...
취소
저장
아직 콘텐츠가 없습니다.