packages feed

Cabal revisions of cluss-0.2

Hackage metadata revisions edit the .cabal file after upload; each diff below is one revision.

revision 1
 name: cluss
 category: type system, constraints
 version: 0.2
+x-revision: 1
 license: BSD3
 license-file: LICENSE
 cabal-version: >= 1.10
 copyright: (c) Yusuke Matsushita 2014
 synopsis: simple alternative to type classes
 description:
-    A __cluss__ enables you to achieve function overloading, or ad-hoc polymorphism,
+    A *cluss* enables you to achieve function overloading, or ad-hoc polymorphism,
     without creating a new type class.
     .
     In order to give ad-hoc polymorphism to a type variable @a@,
         * You can /create/ new methods for clusses anywhere in any module,
         since cluss methods are open.
     .
-    More information can be found in the <http://hackage.haskell.org/package/cluss hackage\'s haddock> or the <https://github.com/Kinokkory/cluss updated haddock>.
+    More information can be found in the <http://hackage.haskell.org/package/cluss hackage's haddock> or the <http://kinokkory.github.io/cluss/ updated haddock>.
 
 build-type: Simple
 
revision 2
 name: cluss
 category: type system, constraints
 version: 0.2
-x-revision: 1
+x-revision: 2
 license: BSD3
 license-file: LICENSE
 cabal-version: >= 1.10
 copyright: (c) Yusuke Matsushita 2014
 synopsis: simple alternative to type classes
 description:
-    A *cluss* enables you to achieve function overloading, or ad-hoc polymorphism,
+    A <b>cluss</b> enables you to achieve function overloading, or ad-hoc polymorphism,
     without creating a new type class.
     .
     In order to give ad-hoc polymorphism to a type variable @a@,
revision 3
 name: cluss
 category: type system, constraints
 version: 0.2
-x-revision: 2
+x-revision: 3
 license: BSD3
 license-file: LICENSE
 cabal-version: >= 1.10
 copyright: (c) Yusuke Matsushita 2014
 synopsis: simple alternative to type classes
 description:
-    A <b>cluss</b> enables you to achieve function overloading, or ad-hoc polymorphism,
+    A /cluss/ enables you to achieve function overloading, or ad-hoc polymorphism,
     without creating a new type class.
     .
     In order to give ad-hoc polymorphism to a type variable @a@,
     The constraint @In [Type T, ...] a@ is what we call a \"cluss\".
     .
     Clusses can easily be used in a nested way
-    and even be __recursive__;
-    therefore, they are /expressive/ enough to imitate Haskell-98-style type classes.
+    and even be /recursive/;
+    therefore, they are expressive enough to imitate Haskell-98-style type classes.
     .
-    Clusses, /however/, go beyond a mere alternative to type classes.
+    Clusses, however, go beyond a mere alternative to type classes.
     They have __closed__ and __prioritized__ instances and __open__ methods,
     while type classes have open and unprioritized instances and closed methods.
     Those properties give clusses the advantages different from type classes:
revision 4
 name: cluss
 category: type system, constraints
 version: 0.2
-x-revision: 3
+x-revision: 4
 license: BSD3
 license-file: LICENSE
 cabal-version: >= 1.10
     therefore, they are expressive enough to imitate Haskell-98-style type classes.
     .
     Clusses, however, go beyond a mere alternative to type classes.
-    They have __closed__ and __prioritized__ instances and __open__ methods,
+    They have /closed/ and /prioritized/ instances and /open/ methods,
     while type classes have open and unprioritized instances and closed methods.
     Those properties give clusses the advantages different from type classes:
     .
-        * You can /judge/ whether a type @a@ belongs to a cluss @'In' as@,
+        * You can judge whether a type @a@ belongs to a cluss @'In' as@,
         on some level, writing @Has as a@,
         since cluss instances are closed.
     .
-        * You can make cluss instances more /flexibly/,
+        * You can make cluss instances more flexibly,
         without causing overlapping instances or incoherent instances,
         since cluss instances are prioritized.
     .
-        * You can /create/ new methods for clusses anywhere in any module,
+        * You can create new methods for clusses anywhere in any module,
         since cluss methods are open.
     .
     More information can be found in the <http://hackage.haskell.org/package/cluss hackage's haddock> or the <http://kinokkory.github.io/cluss/ updated haddock>.