Skip to content

Eliminate possible future bug: keep basins order (no set)#244

Merged
amitmarkel merged 1 commit intomainfrom
amarkel-prepare-limit_n_basins-mode
Feb 18, 2026
Merged

Eliminate possible future bug: keep basins order (no set)#244
amitmarkel merged 1 commit intomainfrom
amarkel-prepare-limit_n_basins-mode

Conversation

@amitmarkel
Copy link
Collaborator

  • slightly improve runtime+memory improvement: basins without excluded ones is computed once
  • safer self.basins (readonly tuple)

It's also a slight runtime+memory improvement: basins without excluded ones is computed once.
@amitmarkel amitmarkel requested a review from omrishefi February 18, 2026 11:09
@amitmarkel amitmarkel changed the title Eliminate possible future bug: keep basins order. Eliminate possible future bug: keep basins order (no set) Feb 18, 2026
Copy link
Collaborator

@omrishefi omrishefi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comment

@amitmarkel amitmarkel requested a review from omrishefi February 18, 2026 11:18
@amitmarkel amitmarkel merged commit 66e5974 into main Feb 18, 2026
2 checks passed
@amitmarkel amitmarkel deleted the amarkel-prepare-limit_n_basins-mode branch February 18, 2026 11:23
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

Successfully merging this pull request may close these issues.

2 participants