-
-
Notifications
You must be signed in to change notification settings - Fork 567
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.
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
Remove Opaque/UnwrapOpaque #823
Open
ethanresnick
wants to merge
1
commit into
sindresorhus:main
Choose a base branch
from
ethanresnick:remove-opaque
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
ethanresnick
force-pushed
the
remove-opaque
branch
18 times, most recently
from
March 4, 2024 21:42
dbbf3f9
to
570a494
Compare
nplusp
reviewed
Apr 3, 2024
We can do a |
ethanresnick
force-pushed
the
remove-opaque
branch
2 times, most recently
from
April 19, 2024 01:13
c795028
to
f575854
Compare
ethanresnick
force-pushed
the
remove-opaque
branch
3 times, most recently
from
April 19, 2024 01:32
6741610
to
9ba360b
Compare
Can you also update the README section "Alternative type names" where Branded redirects to Opaque instead of Tagged? |
ethanresnick
force-pushed
the
remove-opaque
branch
from
April 25, 2024 05:37
9ba360b
to
6f8998c
Compare
@KinderGouello Done, here and in #867. |
ethanresnick
force-pushed
the
remove-opaque
branch
2 times, most recently
from
April 29, 2024 07:48
f871c1c
to
07fbd83
Compare
ethanresnick
force-pushed
the
remove-opaque
branch
from
April 29, 2024 07:51
07fbd83
to
531414d
Compare
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.
This PR may be premature, so I'm happy to let it sit for a bit. But, the basic idea is that:
Tagged
types are strictly more powerful thanOpaque
ones, thanks to their ability to more naturally support multiple tags.Opaque
has always been misnamed (since the underlying, untagged type isn't hidden at all, which is a critical property of opaque types in other languages).Opaque
andUnwrapOpaque
should be removed.