Skip to content

FEAT: add informtation about ComputationStrategy behaviour #16

Description

@Desiment

We decided that we employ policy that each distribution maintains its own computation strategy object. We should describe why we chosen such approach, and add comparison with approach when computation strategy object is universal for multiple distributions objects

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions