Skip to content

Conversation

bjk17
Copy link
Member

@bjk17 bjk17 commented Aug 14, 2019

Instead of the function returning a list of all subrules, it's better to make it into a generator returning each rule as it's generated. This saves memory and opens up for the possibility of parallelising the rule generation (MeshTiling, StringSet and other such objects) and bitstring creation (CombCov).

Also made MeshTiling.get_subrules() a little bit smarted by discarding subrules with empty column or row as those are duplicates of other MeshTilings of lower dimension.

…t_subrules() a little bit smarted by not returning subrules with empty columns or rows (as they're duplicate of smaller MeshTilings)
@bjk17 bjk17 merged commit 224ba6c into master Aug 14, 2019
@bjk17 bjk17 deleted the subrules-generator-instead-of-list branch August 14, 2019 17:19
@coveralls
Copy link

Pull Request Test Coverage Report for Build 103

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 93.805%

Totals Coverage Status
Change from base Build 101: 0.0%
Covered Lines: 106
Relevant Lines: 113

💛 - Coveralls

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