aglinxinyuan opened a new pull request, #7451:
URL: https://github.com/apache/texera/pull/7451

   ### What changes were proposed in this PR?
   
   Deletes `ElidableStatement`, which has no caller and whose mechanism is not 
configured anywhere in the build. Pure deletion, no behaviour change: **−175 
lines**.
   
   | Removed | Lines | Why it is dead |
   | --- | ---: | --- |
   | `engine/common/ElidableStatement.scala` | 34 | no caller; no 
`-Xelide-below` in any `build.sbt` |
   | `engine/common/ElidableStatementSpec.scala` | 141 | covers only the above |
   
   The object wraps statements in `scala.annotation.elidable` so they can be 
compiled out below a threshold. That threshold comes from the `-Xelide-below` 
scalac option, which appears in **no** `build.sbt` in this repo — so the 
wrapper had no effect even in principle. A case-insensitive search for 
`elidable` across all Scala and sbt sources returns only these two files.
   
   > Reviewer note: it acquired unit tests during the 2026 coverage work, which 
is why it currently looks live. The spec covers this object and nothing else, 
so it goes with it.
   
   Split out of #7447, which originally bundled four unrelated removals.
   
   ### Any related issues, documentation, discussions?
   
   Closes #7448
   
   ### How was this PR tested?
   
   Existing tests only — this PR adds none, since it removes code and the spec 
that covered it.
   
   Locally, from the repo root with Java 17:
   
   - `sbt "WorkflowExecutionService/Test/compile"` — success.
   
   Verification, re-runnable by a reviewer:
   
   ```
   git grep -in elidable          # only the two deleted files
   ```
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Claude Opus 5)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to