Skip to content

Finalize @ShadowVariableLooped #1527

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
triceo opened this issue Apr 16, 2025 · 0 comments
Open

Finalize @ShadowVariableLooped #1527

triceo opened this issue Apr 16, 2025 · 0 comments
Assignees

Comments

@triceo
Copy link
Contributor

triceo commented Apr 16, 2025

  • If we know the solution is invalid, why not terminate shadow var evaluation and set them all to null? Could help with performance. (ATM it looks as if we're already doing it.)
  • There are arguments to be made in favor of updating the marker before the variable in question, so that the variable updater could use that information for something. (Unless we decide to ignore the variable in that case altogether.)
  • If a problem cannot loop, make sure loop detection is completely disabled. (Case in point: VRP. VRP never needed loop detection.)
  • Consider a different name for the annotation, based on user feedback. (ShadowVariablesConsistent?)
@triceo triceo added the process/needs triage Requires initial assessment of validity, priority etc. label Apr 16, 2025
@triceo triceo changed the title Finalize behavior of @InvalidityMarker Finalize behavior of @ShadowVariableLooped Apr 20, 2025
@triceo triceo changed the title Finalize behavior of @ShadowVariableLooped Finalize @ShadowVariableLooped Apr 24, 2025
@triceo triceo removed the process/needs triage Requires initial assessment of validity, priority etc. label Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants