Add doc about ref-struct lifetime variance - #9418
Open
agocke wants to merge 3 commits into
Open
Conversation
Member
Author
Member
|
Kinda wary about the number of lifetime docs we have now. Debating if we should just add this directly into the low level struct improvements doc or put it in the expand ref one. |
Member
Author
|
Seems like a fine idea to me. Happy to centralize. I mention at the top that it’s based on the low-level improvements doc. |
Member
|
As long as it's describing existing behavior we should just update the existing doc. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 should wrap up any formalization holes we have around lifetime variance and nested ref fields