Fix some Variable alignment propagation in the simplifier. - #9333
Conversation
…learn_true(varA == varB) is processed. Co-authored-by: Alex Reinking <areinking@adobe.com>
… accidental assignment.
|
Can you add a regression test somewhere? |
|
|
…lp avoid accidental assignment." This reverts commit 90b97b1.
|
Apparently it's preferred to forbid operator= on rvalues on the type in question, rather than return const things (which breaks moving from them). E.g in struct Expr: Note the final |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9333 +/- ##
==========================================
+ Coverage 69.92% 70.04% +0.12%
==========================================
Files 258 258
Lines 78239 78252 +13
Branches 19047 19050 +3
==========================================
+ Hits 54705 54810 +105
+ Misses 17801 17786 -15
+ Partials 5733 5656 -77 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Oops. Working on the regression test. Building on top of your correctness_vector_store_alignment. UPDATE: regression test added in #9337. |
|
I'd argue the clang-tidy warning is just dumb?
It does improve const correctness.
I guess you meant |
…fixed here. Move image checks below the user-defined requirements.
learn_true(x == y)with x and y vars did not fuse their alignment and bounds info.Fixes #9328.
Partial resolution for #9327 by addingconstwhich avoids accidental assignment.Breaking changes
None I'm aware of.
Checklist