Copy constructors and destructors #172
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
* Move the "linearize" pass immediately after "scope", so it's done purely syntactically. * Add "copy" and "destroy" traits and provide default (no-op) instances for built-in types. TODO: * Add tests * Derive these traits implicitly or more concisely (CTE?), correctly calling them for fields of ADTs * Requires generic trait instances to work for generic types * Requires trait constraints
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.
For #156
Move the “linearize” pass immediately after “scope”, so it’s done purely syntactically
Add
copyanddestroytraits and provide default (no-op) instances for built-in typesTODO:
Add tests
Derive these traits implicitly or more concisely (CTE?), correctly calling them for fields of ADTs
Requires generic trait instances to work for generic types
Requires trait constraints
The destructor should be called on the scrutinee of a
matchexpression, after the match is completeAdd warnings when the presence of a nontrivial destructor would inhibit TCO