If I make bins the first argument in all functions in SurveyWeb.Structs.Bins, I will not always be able to pass the piped argument as the first argument in histogram_frequencies/5.
For example, I might get:
|> (&Bins.add_empty_bins(bins, &1)).()
Instead of:
|> Bins.add_empty_bins(bins)
I could make bins the argument of the pipeline in histogram_frequencies/5, instead of ‘responses’. My original idea was not to do that, though, because my app revolves around the concept ‘survey’ – and therefore responses seemed a logical choice for the role of protagonist. For example: “This pipeline turns survey responses into a data-object that a histogram function can process.” instead of “This pipeline turns this bins struct into a data-object that a histogram function can process.”
Any recommendations to what is a better approach, generally speaking? Pick the most logical protagonist for your pipeline, regardless of whether it will be the first argument passed to all segments of the pipeline? Or will I end up regretting |> (&Bins.add_empty_bins(bins, &1)).()?
