fix(frontend): Process intercalating elements in refactoring #252
No reviewers
Labels
No labels
category
bug
category
chore
category
doc
category
feature
category
optimization
category
organization
part/Delation
part/Elab
part/Environment
part/FFI
part/Frontend
part/Goal
part/REPL
part/Serial
priority
high
priority
irrelevant
priority
low
priority
medium
priority
pending-measurement
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: aniva/Pantograph#252
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "frontend/refactor"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is from PutnamBench's
putnam_1997_b1
, where we have declarations:where
property
refers to bothmystery
andauxiliary
.The current solution is to condense the search target in the head decl's environment. This clearly does not work. Therefore, we need to condense the search target in the last decl's environment.
However, in the future we may need to preserve the decl names instead of just squashing them into a new
_composite
decl. In this case, I think we should run two concurrentFrontendM
s, one is for the input file, and one is for the output file.