You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in PR #3729, there is a potential issue with storing addresses of loop variables in the function, which could lead to dangling pointers if gets modified or goes out of scope. Addressing this issue would involve major changes in several parts of the ACTS project and is out of scope for PR #3729. This issue is opened to track the work required to resolve this in a future PR.\n\nRequester: @CarloVarni
The text was updated successfully, but these errors were encountered:
As discussed in PR #3729, there is a potential issue with storing addresses of loop variables in the function, which could lead to dangling pointers if gets modified or goes out of scope. Addressing this issue would involve major changes in several parts of the ACTS project and is out of scope for PR #3729. This issue is opened to track the work required to resolve this in a future PR.\n\nRequester: @CarloVarni
The text was updated successfully, but these errors were encountered: