Documentation of Heap Management Strategy#2750
Open
clemens-k wants to merge 2 commits intoeclipse-score:mainfrom
Open
Documentation of Heap Management Strategy#2750clemens-k wants to merge 2 commits intoeclipse-score:mainfrom
clemens-k wants to merge 2 commits intoeclipse-score:mainfrom
Conversation
|
|
Contributor
|
It should be noted that this PR is based on https://github.com/orgs/eclipse-score/discussions/2457#discussioncomment-16377718 |
istilkerich
suggested changes
Apr 2, 2026
Co-authored-by: istilkerich <isabella.stilkerich@schaeffler.com> Signed-off-by: Clemens Kutz <53788793+clemens-k@users.noreply.github.com>
|
The created documentation from the pull request is available at: docu-html |
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
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.
add: heap avoidance strategy in application assumptions
note: the scope of this PR is limited to alignment of the high-level goal of heap management. Separate PRs will deal with the language specific (Rust, C++, C) coding guidelines.
note 2: I intentionally used the word "should" over "shall" or "must" as we want to avoid heap, but not at all costs. Details of which costs are "acceptable" are language specific and shall be discussed in the coding guideline PRs.
Started after discussion in the architecture community on March 30th, 2026: https://github.com/orgs/eclipse-score/discussions/2457#discussioncomment-16377718