Fixes for changes in how ttg::Buffer takes pointers - #43
Merged
Conversation
nileshchat
reviewed
Jan 28, 2025
All pointers must now be managed so that they don't disappear silently. This needs some adjustment in how we allocate the Domain and gaussian arrays. Signed-off-by: Joseph Schuchart <joseph.schuchart@stonybrook.edu>
devreal
force-pushed
the
ttg-buffer-changes
branch
from
January 28, 2025 01:55
e2e3254 to
a608c30
Compare
Collaborator
Author
|
That was fixed earlier in #44 |
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
2 participants
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.
All pointers must now be managed so that they don't disappear silently. This needs some adjustment in how we allocate the Domain and gaussian arrays.
In preparation for TESSEorg/ttg#301