The search service can find package by either name (apache), provides(webserver), absolute file names (/usr/bin/apache), binaries (gprof) or shared libraries (libXm.so.2) in standard path. It does not support multiple arguments yet...

The System and Arch are optional added filters, for example System could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system.

RPM resource ghc-relude

'relude' is an alternative prelude library. If you find the default 'Prelude' unsatisfying, despite its advantages, consider using 'relude' instead. == Relude goals and design principles * Productivity: You can be more productive with a "non-standard" standard library, and 'relude' helps you with writing safer and more efficient code faster. * Total programming: Usage of partial functions can lead to unexpected bugs and runtime exceptions in pure code. The types of partial functions lie about their behavior. And even if it is not always possible to rely only on total functions, 'relude' strives to encourage best-practices and reduce the chances of introducing a bug. * Type-safety: We use the "make invalid states unrepresentable" motto as one of our guiding principles. If it is possible, we express this concept through the types. Example: ' whenNotNull :: Applicative f => [a] -> (NonEmpty a -> f ()) -> f () ' * Performance: We prefer 'Text' over 'String', use space-leaks-free functions (e.g. our custom performant 'sum' and 'product'), introduce 'INLINE' and 'SPECIALIZE' pragmas where appropriate, and make efficient container types (e.g. 'Map', 'HashMap', 'Set') more accessible. * Minimalism (low number of dependencies): We do not force users of 'relude' to stick to any specific lens or text formatting or logging library. Where possible, 'relude' depends only on boot libraries. * Convenience: Despite minimalism, we want to bring commonly used types and functions into scope, and make available functions easier to use. * Excellent documentation: 1. Tutorial 2. Migration guide from 'Prelude' 3. Haddock for every function with examples tested by doctest 4. Documentation regarding internal module structure 5. 'relude'-specific HLint rules * User-friendliness: Anyone should be able to quickly migrate to 'relude'. Only some basic familiarity with the common libraries like 'text' and 'containers' should be enough (but not necessary). * Exploration: We have space to experiment with new ideas and proposals without introducing breaking changes. 'relude' uses the approach with 'Extra.*' modules which are not exported by default. The chosen approach makes it quite easy for us to provide new functionality without breaking anything and let the users decide to use it or not.

Found 1 sites for ghc-relude

• https://hackage.haskell.org/package/relude

Found 20 RPM for ghc-relude

Generated by rpm2html 1.6

Fabrice Bellet