Nullable type #1602
Merged
Nullable type #1602
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Jubilee <46493976+workingjubilee@users.noreply.github.com>
|
As I mentioned while discussing this offsides, I have some other thoughts about the way the traits carve up the world that I think are better proposed as a refactoring since it's hard to really think them through in the review/talking format. |
workingjubilee
approved these changes
Mar 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add an
Option-like type to distinguish "This element is out-of-bounds" from "This element is a Postgresnull", as well as genericizing over NullLayout types that mark where null elements are in a container (for example, the null bitslice on arrays).This is meant to implement the behavior requested in #620 and #1586
For iterators, a separate pull request has been split off: NotGyro#2