Fix use-after-move cases - #3390
Open
andrjohns wants to merge 1 commit into
Open
Conversation
Member
I think we could extend the test generation we use for expressions to generate calls with temporaries, maybe? Could not be worth the hassle |
WardBrian
approved these changes
Sep 6, 2026
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.
Summary
There were two cases in the Math library which used a matrix input after
std::forward-ing it into arefor anarenatype. This wasn't an issue unless rvalues were passed as inputs, at which point theref/arenawould move-construct and leave an empty matrix:I (and claude) could only find this in the
revoverloads forcholesky_decomposeandcolumns_dot_product, but not sure if there's a good way to add a more universal test for this.Tests
N/A - tests should still pass
Side Effects
N/A
Release notes
Fix use-after-move in
cholesky_decomposeandcolumns_dot_productChecklist
Copyright holder: (fill in copyright holder information)
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
the basic tests are passing
./runTests.py test/unit)make test-headers)make test-math-dependencies)make doxygen)make cpplint)the code is written in idiomatic C++ and changes are documented in the doxygen
the new changes are tested