ENH: use objectRegistry/IOobjectList sorted instead of lookupClass (db16d808) · Commits · Development / openfoam

Snippets Groups Projects

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Commit db16d808 authored 1 year ago by

Mark OLESEN

Browse files

ENH: use objectRegistry/IOobjectList sorted instead of lookupClass

- in most cases a parallel-consistent order is required.
  Even when the order is not important, it will generally require
  fewer allocations to create a UPtrList of entries instead of a
  HashTable or even a wordList.

parent d65e2d89

1 merge request!617Updates to function objects handling of patches / selection names for parallel consistent order

Hide whitespace changes

Inline Side-by-side

Showing with 550 additions and 678 deletions

Please register or to comment

Admin message

ENH: use objectRegistry/IOobjectList sorted instead of lookupClass