Metadata revisions for semigroupoids-5.3.6

Package maintainers and Hackage trustees are allowed to edit certain bits of package metadata after a release, without uploading a new tarball. Note that the tarball itself is never changed, just the metadata that is stored separately. For more information about metadata revisions, please refer to the Hackage Metadata Revisions FAQ.

No. Time User SHA256
-r3 (semigroupoids-5.3.6-r3) 2023-02-02T15:17:02Z ryanglscott b00521e62531d3524c6ac285ccc0047bf6ce54fa622341b14323f804debecb5d
  • Changed the library component's library dependency on 'base' from

    >=4.3 && <5
    to
    >=4.3 && <4.18

-r2 (semigroupoids-5.3.6-r2) 2021-11-09T19:49:22Z ryanglscott 56119f42bc080256100bd6dab6292c144eef430b3430f2ce1581e8e06668d33e
  • Changed the library component's library dependency on 'hashable' from

    >=1.2.7.0 && <1.4
    to
    >=1.2.7.0 && <1.5

  • Changed the library component's library dependency on 'hashable' from

    >=1.2.5.0 && <1.4
    to
    >=1.2.5.0 && <1.5

-r1 (semigroupoids-5.3.6-r1) 2021-10-09T22:22:53Z ryanglscott 095698e4a67d419f5a7e1ca2cbfcf3337fe0633257f97938bb0ba1d2919ecb46
  • Changed description from

    Provides a wide array of (semi)groupoids and operations for working with them.
    
    A 'Semigroupoid' is a 'Category' without the requirement of identity arrows for every object in the category.
    
    A 'Category' is any 'Semigroupoid' for which the Yoneda lemma holds.
    
    When working with comonads you often have the @\<*\>@ portion of an @Applicative@, but
    not the @pure@. This was captured in Uustalu and Vene's \"Essence of Dataflow Programming\"
    in the form of the @ComonadZip@ class in the days before @Applicative@. Apply provides a weaker invariant, but for the comonads used for data flow programming (found in the streams package), this invariant is preserved. Applicative function composition forms a semigroupoid.
    
    Similarly many structures are nearly a comonad, but not quite, for instance lists provide a reasonable 'extend' operation in the form of 'tails', but do not always contain a value.
    
    We describe the relationships between the type classes defined in this package
    and those from `base` (and some from `contravariant`) in the diagram below.
    Thick-bordered nodes correspond to type classes defined in this package;
    thin-bordered ones correspond to type classes from elsewhere. Solid edges
    indicate a subclass relationship that actually exists; dashed edges indicate a
    subclass relationship that /should/ exist, but currently doesn't.
    
    <<img/classes.svg Relationships among type classes from this package and others>>
    
    Apply, Bind, and Extend (not shown) give rise the Static, Kleisli and Cokleisli semigroupoids respectively.
    
    This lets us remove many of the restrictions from various monad transformers
    as in many cases the binding operation or @\<*\>@ operation does not require them.
    
    Finally, to work with these weaker structures it is beneficial to have containers
    that can provide stronger guarantees about their contents, so versions of 'Traversable'
    and 'Foldable' that can be folded with just a 'Semigroup' are added.
    to
    Provides a wide array of (semi)groupoids and operations for working with them.
    
    A 'Semigroupoid' is a 'Category' without the requirement of identity arrows for every object in the category.
    
    A 'Category' is any 'Semigroupoid' for which the Yoneda lemma holds.
    
    When working with comonads you often have the @\<*\>@ portion of an @Applicative@, but
    not the @pure@. This was captured in Uustalu and Vene's \"Essence of Dataflow Programming\"
    in the form of the @ComonadZip@ class in the days before @Applicative@. Apply provides a weaker invariant, but for the comonads used for data flow programming (found in the streams package), this invariant is preserved. Applicative function composition forms a semigroupoid.
    
    Similarly many structures are nearly a comonad, but not quite, for instance lists provide a reasonable 'extend' operation in the form of 'tails', but do not always contain a value.
    
    We describe the relationships between the type classes defined in this package
    and those from `base` (and some from `contravariant`) in the diagram below.
    Thick-bordered nodes correspond to type classes defined in this package;
    thin-bordered ones correspond to type classes from elsewhere. Solid edges
    indicate a subclass relationship that actually exists; dashed edges indicate a
    subclass relationship that /should/ exist, but currently doesn't.
    
    <<https://raw.githubusercontent.com/ekmett/semigroupoids/b9151e725856265717fe462c7abe4e59417ec593/img/classes.svg Relationships among type classes from this package and others>>
    
    Apply, Bind, and Extend (not shown) give rise the Static, Kleisli and Cokleisli semigroupoids respectively.
    
    This lets us remove many of the restrictions from various monad transformers
    as in many cases the binding operation or @\<*\>@ operation does not require them.
    
    Finally, to work with these weaker structures it is beneficial to have containers
    that can provide stronger guarantees about their contents, so versions of 'Traversable'
    and 'Foldable' that can be folded with just a 'Semigroup' are added.

-r0 (semigroupoids-5.3.6-r0) 2021-10-07T23:42:11Z ryanglscott 42153e9911c7fab27372df858799a826ed6b324af648b561297846806f976d6b