Skip to content

Nonblocking backend improvements #250

@anyzelman

Description

@anyzelman
  • nonblocking/coordinates.hpp misses omp/config.hpp include.
  • lazy evaluation could be a singleton class, which would preclude having to declare an external grb::internal::le variable whenever it is used?
  • analytic_model, pipeline, and lazy_evaluation should be template classes parametrised in the backend?
  • related configs to the analytic model etc. should also be parametrised in the backend.

Rationale for the last two points: we ran into the case where we have a different use case for nonblocking execution that requires minor modification of some of these classes, but currently have no way that enables easy code reuse / co-existence of two nonblocking backends that reuses some of the infrastructure.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions