Difference between revisions of "The Other Prelude"
Jump to navigation
Jump to search
m (added links to other proposa pages, added page to Category:Proposals) |
BrettGiles (talk | contribs) (Title conventions on hawiki pages) |
||
Line 1: | Line 1: | ||
[[Category:Proposals]] |
[[Category:Proposals]] |
||
− | == Call for |
+ | == Call for contribution == |
This fun project, called "The Other Prelude", and is a creative reconstruction of the standard Prelude. By disregarding history and compatibility, we get a clean sheet. |
This fun project, called "The Other Prelude", and is a creative reconstruction of the standard Prelude. By disregarding history and compatibility, we get a clean sheet. |
||
− | == Naming |
+ | == Naming conventions == |
The principal is to make the names very readable for both beginners and category theorists (if any). |
The principal is to make the names very readable for both beginners and category theorists (if any). |
||
Line 15: | Line 15: | ||
− | == The |
+ | == The hierarchy == |
* <hask>TheOtherPrelude</hask> - Minimalistic module. |
* <hask>TheOtherPrelude</hask> - Minimalistic module. |
||
* <hask>TheOtherPrelude.Extension</hask> - Convenient definitions. |
* <hask>TheOtherPrelude.Extension</hask> - Convenient definitions. |
||
− | == The |
+ | == The code == |
Currently, the code is in Wiki form. If people do agree that the collaborative decisions begot something pretty, we'll have a group of files in darcs.haskell.org some time. |
Currently, the code is in Wiki form. If people do agree that the collaborative decisions begot something pretty, we'll have a group of files in darcs.haskell.org some time. |
||
Line 51: | Line 51: | ||
</haskell> |
</haskell> |
||
− | == See |
+ | == See also == |
* [[Mathematical prelude discussion]] - A numeric Prelude. Could this be merged into this one? |
* [[Mathematical prelude discussion]] - A numeric Prelude. Could this be merged into this one? |
||
* [[Prelude extensions]] and [[Prelude function suggestions]] - Unlike "The Other Prelude" they ''enhance'' the Prelude. |
* [[Prelude extensions]] and [[Prelude function suggestions]] - Unlike "The Other Prelude" they ''enhance'' the Prelude. |
Revision as of 14:08, 21 December 2006
Call for contribution
This fun project, called "The Other Prelude", and is a creative reconstruction of the standard Prelude. By disregarding history and compatibility, we get a clean sheet.
Naming conventions
The principal is to make the names very readable for both beginners and category theorists (if any).
Guidelines
- The prelude should not contain any "projection" functions (like
fst
andsnd
. They go to the Extension module.
Issues
- Should alphanumeric names be preferred over symbols when defining a class?
The hierarchy
TheOtherPrelude
- Minimalistic module.TheOtherPrelude.Extension
- Convenient definitions.
The code
Currently, the code is in Wiki form. If people do agree that the collaborative decisions begot something pretty, we'll have a group of files in darcs.haskell.org some time.
The imaginery Prelude as it stands,
import Prelude () -- hide everything
-- the idea is to remove 'fmap'
-- and map :: (a -> b) -> [a] -> [b] to be a special case
class Functor f where
map :: (a -> b) -> f a -> f b
-- should the Functor hierarchy proposal be adopted?
class Monad m where
(>>=) :: m a -> (a -> m b) -> m b
(>>) :: m a -> m b -> m b
return :: a -> m a
fail :: String -> m a
How to use it, as it stands,
import Prelude () -- hide everything
import TheOtherPrelude -- get everything
import qualified TheOtherPrelude.Monad as M -- standard convention
See also
- Mathematical prelude discussion - A numeric Prelude. Could this be merged into this one?
- Prelude extensions and Prelude function suggestions - Unlike "The Other Prelude" they enhance the Prelude.
- Functor hierarchy proposal - making "Monad m" imply "Functor m"
- If-then-else - making "if" a function