Skip to content

"linking" instead of "loading" #10

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

Merged
merged 1 commit into from
May 1, 2015
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions FutureFeatures.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,10 @@ of the [Minimum Viable Product](V1.md) or the
to be standardized immediately after v.1. These will be prioritized based on
developer feedback.

## Dynamic loading
* Both load-time and run-time.
## Dynamic linking
* [Dynamic loading](V1.md#code-loading-and-imports) is in [v.1](V1.md), but all loaded modules have
their own [separate heaps](V1.md#heap) and cannot share [function pointers](V1.md#function-pointers).
* Support both load-time and run-time (`dlopen`) dynamic linking.
* TODO

## Finer-grained control over memory
Expand Down