Skip to content

ASP-based solver: use a unique ID counter#41290

Merged
alalazo merged 3 commits intospack:developfrom
alalazo:refactor/use-a-unique-counter
Nov 28, 2023
Merged

ASP-based solver: use a unique ID counter#41290
alalazo merged 3 commits intospack:developfrom
alalazo:refactor/use-a-unique-counter

Conversation

@alalazo
Copy link
Copy Markdown
Member

@alalazo alalazo commented Nov 28, 2023

Just an internal change we agreed on. The solver now uses a unique counter for "conditions", "triggers", and "effects".

@spackbot-app spackbot-app bot added the core PR affects Spack core functionality label Nov 28, 2023
@alalazo alalazo merged commit 0e65e84 into spack:develop Nov 28, 2023
@alalazo alalazo deleted the refactor/use-a-unique-counter branch November 28, 2023 15:28
@alalazo alalazo mentioned this pull request Jan 2, 2024
36 tasks
alalazo added a commit that referenced this pull request Jan 2, 2024
* solver: use a unique counter for condition, triggers and effects

* Do not reset counters when re-running setup

  What we need is just a unique ID, it doesn't need
  to start from zero every time.
alalazo added a commit that referenced this pull request Jan 10, 2024
* solver: use a unique counter for condition, triggers and effects

* Do not reset counters when re-running setup

  What we need is just a unique ID, it doesn't need
  to start from zero every time.
haampie pushed a commit that referenced this pull request Jan 11, 2024
* solver: use a unique counter for condition, triggers and effects

* Do not reset counters when re-running setup

  What we need is just a unique ID, it doesn't need
  to start from zero every time.
RikkiButler20 pushed a commit to RikkiButler20/spack that referenced this pull request Jan 31, 2024
* solver: use a unique counter for condition, triggers and effects

* Do not reset counters when re-running setup

  What we need is just a unique ID, it doesn't need
  to start from zero every time.
vjranagit pushed a commit to vjranagit/spack that referenced this pull request Jan 18, 2026
* solver: use a unique counter for condition, triggers and effects

* Do not reset counters when re-running setup

  What we need is just a unique ID, it doesn't need
  to start from zero every time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core PR affects Spack core functionality refactoring

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants