Dmitrii Kovanikov

Sometimes we want to add more features to `universum`. But we don't want them be imported implicitly in every module. But instead of creating separate package `universum-exended` we can have...

Sometimes it's convenient to map `bimap` and related functions inside some `Functor`. For example, if your data base returns `Either` inside `IO`. It might be slightly les convenient to write...

I propose to add very dummy and stupid test to verify that changes in `universum` don't remove something from imports: just add dummy module in `test-suite` which reexports whole `universum`...

Some type classes are not very common even if they are very useful. Maybe it's better to move them away from default reexport. Here is the list of such type...

Optional chaining syntax: the ?. operator

8

Dhall is amazing when it comes to getting and setting fields of nested records. However, when those fields are wrapped into some types (e.g. `Optional`), then you need to use...

`base-4.16` started to reexport the unary tuple type `Solo` from the `Data.Tuple` module. A data type like this one is helpful in various library. I'm usually using `Only` from the...

[RFC] Add 'append'

1

The following function: ```haskell append :: Semigroup a => a -> a -> a append = () ``` I think it can be useful and beginner-friendly 🙂 Especially with more...

Formatting a file with stylish-haskell results in future parsing errors by stylish-haskell

2

Using the latest version of `stylish-haskell` to format a particular file inplace changes the content of the file, and when running `stylish-haskell` again on this file, it doesn't parse anymore....

Consider file with next imports: ```haskell import Distribution.PackageDescription (BuildInfo (includeDirs) , GenericPackageDescription (packageDescription)) ``` When I run `stylish-haskell` over such file current import is aligned in the next less desirable...