Fix missing metadata
when operation and resulting BasicSymbolic
subtype mismatch
#632
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.
This PR addresses an issue in the
basicsymbolic
function where it incorrectly assumes that the+
and*
operations always result inAdd
andMul
objects, respectively.SymbolicUtils.jl/src/types.jl
Lines 589 to 600 in 2ec473e
Currently, when arguments possess metadata, the operations might return a
Term
object instead, as seen inSymbolicUtils.jl/src/types.jl
Lines 1082 to 1083 in 2ec473e
SymbolicUtils.jl/src/types.jl
Lines 1136 to 1138 in 2ec473e
This inconsistency was causing problems in Vaibhavdixit02/SymbolicAnalysis.jl#43 (comment)
This PR corrects this problem by explicitly handling the
Term
case. This ensures themaketerm
function behaves consistently and correctly handles arguments with metadata.