Renamed to hayleigh-dot-dev/tuple-extra. It is published under that name, and new versions come out there.
Versions published as pd-andy/tuple-extra still install under that name. 2 versions of 2 come from the new location (see their notes).
Rerouted (renamed, needs approval). The GitHub user or repository was renamed. The tag is still there, at the new name. The Lamdera package server serves a copy recovered from https://github.com/hayleigh-dot-dev/tuple-extra.
What we checked: The repo moved to github.com/hayleigh-dot-dev/tuple-extra and tag 1.0.0 is there; its commit 52f61de1db62 is from 2022-02-21 08:58 UTC, after the version was published (2019-12-18 22:06 UTC); elm.json differs from package.elm-lang.org's; the exposed modules match docs.json; the zip's SHA-1 is not the published one and nothing else confirms its contents.
We could not verify this copy against what was published, so the Lamdera compiler asks before using it (y/n). Without a terminal, as in CI, it stops with an error unless approved:
lamdera make --auto-approve-package-rerouting approves rerouted versions for that run,LAMDERA_AUTO_APPROVE_PACKAGE_REROUTING=1 does the same for every run in that environment,LAMDERA_CACHE=off skips the Lamdera package server altogether: packages come from package.elm-lang.org and GitHub only, as with elm, and a rerouted version then fails to download.Details · package.elm-lang.org's zip: https://github.com/pd-andy/tuple-extra/zipball/1.0.0/
In certain situations, this proves more "pipe friendly" than the standard
Tuple.pair. Fits nicely in your update function.
{ model | count = model.count + 1 }
|> Tuple.pairWith Cmd.noneOccasionally you might want to create a Tuple from a single value. This does just that.
Tuple.from 1
== (1, 1)Given a function that takes two arguments, apply that function to the two values contained in a tuple.
Tuple.apply (+) (1, 2)
== 3Flip the two values contained in a tuple.
Similar to String.join but for tuples instead of lists. Given some separator string, join together two strings in a tuple.
Tuple.join " " ("Hello", "world")
== "Hello world"Works just like join, but first converts the values of the tuple to strings. These means the function works with any type of tuple.
Tuple.joinBy String.fromInt suitToString " of " (7, Club)
== "Seven of Clubs"Similar to List.sum but for tuples instead of lists. Adds together two numbers contained in a tuple.
Tuple.sum (1, 2)
== 3Similar to List.sum but for tuples instead of lists. Multiplies together two numbers contained in a tuple
Tuple.product (1, 2)
== 2Similar to List.sort but for tuples instead of lists. Sort values contained in a tuple from lowest to highest
Tuple.sort (2, 1)
== (1, 2)Similar to List.sortBy but for tuples instead of lists. Sort values
contained in a tuple by first converting both values to a comparable. The
values are sorted lowest to highest
Tuple.sortBy String.length ("mouse", "cat")
== ("cat", "mouse")Similar to List.sortWith but for tuples instead of lists. Instead of
converting values contained in a tuple to comparables, instead supply a
function that will produce an Order directly.
Tuple.sortWith Basics.compare (2, 1)
== Tuple.sort (2, 1)
== (1, 2)Apply a function to both values contained in a tuple. This might also be
known as mapBothWith or bimap.
Tuple.map negate (-3, 10)
== (3, -10)Occasionally you might find yourself in a situation where both values
contained in a tuple a Maybes. Sometimes it makes more sense to take those
values and make the tuple a Maybe instead.
Tuple.sequenceMaybe (Just 10, Nothing)
== Nothing
Tuple.sequenceMaybe (Just 10, Just "Cat")
== Maybe (10, "Cat")Similar to sequenceMaybe but only looks at the first value in a tuple
to check for nothingness.
Tuple.sequenceFirstMaybe (Just 10, "Cat")
== Maybe (10, "Cat")Similar to sequenceMaybe but only looks at the first value in a tuple
to check for nothingness.
Tuple.sequenceFirstMaybe (10, Just "Cat")
== Maybe (10, "Cat")
By type aliasing tuples into a "normal" type, we remove the (small) effort required in reading types and signatures that have tuples in. I've found this is most beneficial when a tuple is nested inside another type. Visually, the Tuple type is now no different to List, Maybe, or Result.
For example, this:
becomes: