Skip to content

Document Operator architecture a bit better #1319

@fhennig

Description

@fhennig

As a newcomer, the Operator idea isn't so obvious.

IMO it would be sufficient to add some Javadoc to the interface, that could be the central place to explain the concept.

The main question to answer is: Why this over simply composing function calls as usual?

From my call with Chaoran I remember:

  • It's easier to cache things
  • In theory we could optimize queries (not implemented yet)
  • Something with a potentially central executor?

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