memory: Make backend interface more low level #446
Merged
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.
The backend interface of
memory
expects the dynamic memory type to dispatch to the correct platform-specific call. However, this introduces a cyclic dependency to the high-levelmemory
interface. Furthermore, dispatching should not be part of the backend logic as the backends should only provide the implementations of small building blocks which, in turn, are used to build the entire business logic. Redesign the backend API by splitting the malloc/free/memcpy functions into low-level pieces tied to a specific memory type configuration and move the respective dispatching logic up to the high-level shared implementation.