STYLE: consistent use of wordHashSet instead of HashSet<word>

- the wordHashSet typedef is always available when HashSet has been
  included.

- use default HashTable key (word) instead of explicitly mentioning it
This commit is contained in:
Mark Olesen
2018-02-22 11:19:47 +01:00
parent f95f8bf512
commit 37e248c74b
54 changed files with 108 additions and 117 deletions

View File

@ -40,7 +40,7 @@ template<template<class> class CombineOp>
void MapMesh
(
const meshToMesh& interp,
const HashSet<word>& selectedFields,
const wordHashSet& selectedFields,
const bool noLagrangian
)
{

View File

@ -121,7 +121,7 @@ template<class Type, class CombineOp>
void MapVolFields
(
const IOobjectList& objects,
const HashSet<word>& selectedFields,
const wordHashSet& selectedFields,
const meshToMesh& interp,
const CombineOp& cop
)

View File

@ -47,7 +47,7 @@ void mapConsistentMesh
const word& mapMethod,
const word& AMIMapMethod,
const bool subtract,
const HashSet<word>& selectedFields,
const wordHashSet& selectedFields,
const bool noLagrangian
)
{
@ -86,7 +86,7 @@ void mapSubMesh
const word& mapMethod,
const word& AMIMapMethod,
const bool subtract,
const HashSet<word>& selectedFields,
const wordHashSet& selectedFields,
const bool noLagrangian
)
{
@ -260,7 +260,7 @@ int main(int argc, char *argv[])
Info<< "Subtracting mapped source field from target" << endl;
}
HashSet<word> selectedFields;
wordHashSet selectedFields;
args.readIfPresent("fields", selectedFields);
const bool noLagrangian = args.found("noLagrangian");