Changelog for ghc-bifunctors-5.6.2-1.105.x86_64.rpm :

* Tue Mar 19 2024 Peter Simons - Update bifunctors to version 5.6.2. Upstream has edited the change log file since the last release in a non-trivial way, i.e. they did more than just add a new entry at the top. You can review the file at: http://hackage.haskell.org/package/bifunctors-5.6.2/src/CHANGELOG.markdown
* Sun Mar 17 2024 Peter Simons - Update bifunctors to version 5.6.1 revision 3. Upstream has revised the Cabal build instructions on Hackage.
* Sat Sep 30 2023 Peter Simons - Update bifunctors to version 5.6.1 revision 2. 5.6.1 [2023.03.13] - -----------------
* Provide instances for the `Swap` and `Assoc` type classes from the `assoc` package. (These instances were previously defined in `assoc` itself, but they have been migrated over to `bifunctors` in tandem with the `assoc-1.1` release.)
* Only depend on `bifunctor-classes-compat` if building with GHC 8.0. 5.6 [2023.03.12] - ---------------
* Drop support for GHC 7.10 and earlier.
* Move the `Data.Bifunctor`, `Data.Bifoldable`, and `Data.Bitraversable` compatibility modules to the new `bifunctor-classes-compat` package. For backwards compatibility, the `bifunctors` library re-exports `Data.Bifoldable` and `Data.Bitraversable` modules from `bifunctor-classes-compat` when building with GHC 8.0. If your library depends on `bifunctors` and compiles with pre-8.2 versions of GHC, be warned that it may be possible to construct a build plan involving a pre-`5.6` version of `bifunctors` where:
* Some of the `Bifunctor` instances come from `bifunctor-classes-compat`\'s compatibility classes, and
* Other `Bifunctor` instances come from `bifunctors`\'s compatibility classes. These compatibility classes are distinct, so this could lead to build errors under certain conditions. Some possible ways to mitigate this risk include:
* Drop support for GHC 8.0 and older in your library.
* Require `bifunctors >= 5.6` in your library.
* If neither of the options above are viable, then you can temporarily define instances for the old compatibility classes from `bifunctors` like so: ```hs - - For Bifunctor instances import qualified \"bifunctor-classes-compat\" Data.Bifunctor as BifunctorCompat [#]if !MIN_VERSION_bifunctors(5,6,0) && !MIN_VERSION_base(4,8,0) import qualified \"bifunctors\" Data.Bifunctor as Bifunctor [#]endif instance BifunctorCompat.Bifunctor MyType where ... [#]if !MIN_VERSION_bifunctors(5,6,0) && !MIN_VERSION_base(4,8,0) instance Bifunctor.Bifunctor MyType where ... [#]endif ``` ```hs - - For Bifoldable and Bitraversable instances import qualified \"bifunctor-classes-compat\" Data.Bifoldable as BifoldableCompat import qualified \"bifunctor-classes-compat\" Data.Bitraversable as BitraversableCompat [#]if !MIN_VERSION_bifunctors(5,6,0) && !MIN_VERSION_base(4,10,0) import qualified \"bifunctors\" Data.Bifoldable as Bifoldable import qualified \"bifunctors\" Data.Bitraversable as Bitraversable [#]endif instance BifoldableCompat.Bifoldable MyType where ... instance BitraversableCompat.Bitraversable MyType where ... [#]if !MIN_VERSION_bifunctors(5,6,0) && !MIN_VERSION_base(4,10,0) instance Bifoldable.Bifoldable MyType where ... instance Bitraversable.Bitraversable MyType where ... [#]endif ``` If your package does nothing but define instances of `Bifunctor` _et al._, you may consider replacing your `bifunctors` dependency with `bifunctor-classes-compat` to reduce your dependency footprint. If you do, it is strongly recommended that you bump your package\'s major version number so that your users are alerted to the details of the migration.
* Define a `Foldable1` instance for `Joker`, and define `Bifoldable1` instances for `Biff`, `Clown`, `Flip`, `Join`, `Joker`, `Product`, `Tannen`, and `WrappedBifunctor`. These instances were originally defined in the `semigroupoids` library, and they have now been migrated to `bifunctors` as a side effect of adapting to [this Core Libraries Proposal](https://github.com/haskell/core-libraries-committee/issues/9), which adds `Foldable1` and `Bifoldable1` to `base`.
* Thu Mar 30 2023 Peter Simons - Updated spec file to conform with ghc-rpm-macros-2.5.2.
* Mon Feb 27 2023 Peter Simons - Update bifunctors to version 5.5.15. 5.5.15 [2023.02.27] - ------------------
* Support `th-abstraction-0.5.
*`.
* Thu Dec 08 2022 Peter Simons - Update bifunctors to version 5.5.14. 5.5.14 [2022.12.07] - ------------------
* Define `Functor`, `Foldable`, and `Traversable` instances for `Sum` and `Product`.
* Mon Sep 12 2022 Peter Simons - Update bifunctors to version 5.5.13. 5.5.13 [2022.09.12] - ------------------
* Make the `Biapplicative` instances for tuples lazy, to match their `Bifunctor` instances.
* Sat Jul 23 2022 Peter Simons - Update bifunctors to version 5.5.12 revision 1. Upstream has revised the Cabal build instructions on Hackage.
* Sun May 08 2022 Peter Simons - Update bifunctors to version 5.5.12. 5.5.12 [2022.05.07] - ------------------
* Backport an upstream GHC change which removes the default implementation of `bitraverse`. Per the discussion in https://github.com/haskell/core-libraries-committee/issues/47, this default implementation was completely broken, as attempting to use it would always result in an infinite loop.
* Wed Aug 04 2021 psimonsAATTsuse.com- Update bifunctors to version 5.5.11 revision 1. Upstream has revised the Cabal build instructions on Hackage.
* Fri Apr 30 2021 psimonsAATTsuse.com- Update bifunctors to version 5.5.11. 5.5.11 [2021.04.30] - ------------------
* Allow building with `template-haskell-2.18` (GHC 9.2).
* Sun Jan 24 2021 psimonsAATTsuse.com- Update bifunctors to version 5.5.10. 5.5.10 [2021.01.21] - ------------------
* Fix a bug in which `deriveBifoldable` could generate code that triggers `-Wunused-matches` warnings.