docs: update memory.md #1435
Merged
docs: update memory.md #1435
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
I've added some additional context to the doc in efforts to explain the memory management system to users. After this, I'm going to write a bit more about the actual implementation of the system as it stands currently. One of the goals of this effort is to make it easier to upgrade given an exhaustive account of its present workings.
The start of some additional introductory documentation on the memory management system's key operations.
Describes the basics of copying references. More to come.
The memory doc now contains an approachable explanation of basic linear type system concepts. I plan on extending this exploration with some detailed explorations of the implementation.
hellerve
approved these changes
Oct 27, 2022
- Remove a comma. - Mention registered types.
eriksvedang
approved these changes
Oct 28, 2022
TimDeve
reviewed
Oct 28, 2022
- Fix a typo - Mention `ref` - Describe that `typedef` defined types are automatically given delete implementations and managed by default.
scolsen
added a commit
to scolsen/Carp
that referenced
this pull request
Nov 1, 2022
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.
I wanted to better understand Carp's memory management system before diving in to fix some things, so I figured I'd write about it to enhance my own understanding. First off, however, I felt it might be nice to have a general, relatively approachable introduction to the general concepts behind a linear type system for newcomers to reference. Part of this was sparked by @eriksvedang's insightful comment that lifetimes have much to do with multiple scopes and moving values across different lexical bindings.