Skip to content
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.

Reconsider the naming of func (sw *Scribe) Run(step ...Steps) #25

Open
kminehart opened this issue Mar 14, 2022 · 0 comments
Open

Reconsider the naming of func (sw *Scribe) Run(step ...Steps) #25

kminehart opened this issue Mar 14, 2022 · 0 comments

Comments

@kminehart
Copy link
Collaborator

Because Run is a verb (and a common one in software development), many users would expect that it does something "now", as in, at the moment of being called.

Instead, it adds a list of steps to the collection which will run one after another, in a "sequence". Another function with a more appropriate name is Parallel(step ...Steps), which will run the listed steps in parallel or concurrently whenever the pipeline is executed.

Some options:

  • Sequence(step ...Steps)
  • Serial(step ...Steps)
@kminehart kminehart changed the title Reconsider the naming of func (sw *Shipwright) Run(step ...Steps) Reconsider the naming of func (sw *Scribe) Run(step ...Steps) Jun 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant