# # #
_oo0oo_
o88888o
88" . "88
(| -_- |)
0\ = /0
___/`---'\____
.' \| |// '.
/ /||| : |||/\ \
| _|\||| -:- ||||| \
/ | \\ - /// |\ \
| \_| ''\---/'' |/ |
\ .-\__ '-' ___/-. /
___'. .' /--.--\ `. .'___
."" '< `.___\_<|>_/___.' >' "".
| | : `- \`.;`\ _ /`;.`/ - ` : | |
\ \ `_. \_ __\ /__ _/ .-` / /
=====`-.____`.___ \_____/___.-`___.-'=====
`=---='
# # #
“Employ your time in improving yourself by other men’s writings so that you shall come easily by what others have labored hard for.” (Socrates by Plato)
Important notes on Haskell, category theory & related fields, terms and recommendations.
Book comes in forms:
This book is created using complex Org markup file with a lot of LaTeX and LaTeX formulas. Be aware - GitHub & GitLab only partially parse Org into HTML.
To get the full view:
- Outline navigation
- LaTeX formulas:
\( {\displaystyle\left[{-\frac{\hbar2}{2m}}∇2+V(\vec{r},t)\right]Ψ({\vec{r}},t)=i\hbar{∂\over∂{t}}Ψ({\vec{r}},t),\quad\sumk,j\left[-{\frac{\hbar2}{\sqrt{a}}}{\frac{∂}{∂{qk}}}\left({\sqrt{a}}akj{\frac{∂}{∂{qj}}}\right)+V\right]Ψ+{\frac{\hbar}{i}}{\frac{∂{Ψ}}{∂{t}}}=0} \)
- Interlinks: <<<Interlinks>>>
, please refere to Web book, PDF, LaTeX, of use Org-mode capable viewer/editor.
Note about the markup: <<<This is a radio target>>>
- is the ancor for dynamic linking.
Users of Emacs
can prettify radio targets to be shown as hyper-links with this Elisp
snippet:
;;;; 2019-06-12: NOTE:
;;;; Prettify '<<<Radio targets>>>' to be shown as '_Radio_targets_',
;;;; when `org-descriptive-links` set.
;;;; This is improvement of the code from: Tobias&glmorous:
;;;; https://emacs.stackexchange.com/questions/19230/how-to-hide-targets
;;;; There exists library created from the sample:
;;;; https://github.com/talwrii/org-hide-targets
(defcustom org-hidden-links-additional-re "\\(<<<\\)[[:print:]]+?\\(>>>\\)"
"Regular expression that matches strings where the invisible-property
of thesub-matches 1 and 2 is set to org-link."
:type '(choice (const :tag "Off" nil) regexp)
:group 'org-link)
(make-variable-buffer-local 'org-hidden-links-additional-re)
(defun org-activate-hidden-links-additional (limit)
"Put invisible-property org-link on strings matching
`org-hide-links-additional-re'."
(if org-hidden-links-additional-re
(re-search-forward org-hidden-links-additional-re limit t)
(goto-char limit)
nil))
(defun org-hidden-links-hook-function ()
"Add rule for `org-activate-hidden-links-additional'
to `org-font-lock-extra-keywords'.
You can include this function in `org-font-lock-set-keywords-hook'."
(add-to-list 'org-font-lock-extra-keywords
'(org-activate-hidden-links-additional
(1 '(face org-target invisible org-link))
(2 '(face org-target invisible org-link)))))
(add-hook 'org-font-lock-set-keywords-hook #'org-hidden-links-hook-function)
SCHT:
and metadata in :properties:
- of my org-drill
practices, please just run org-drill-strip-all-data
.
- Introduction
- Definitions
- <<<Algebra>>>
- <<<Category theory>>>
- /*/
- <<<Abelian category>>>
- <<<Composition>>>
- <<<Endofunctor category>>>
- <<<Functor>>>
- /*/
- <<<Power set functor>>>
- <<<Forgetful functor>>>
- <<<Identity functor>>>
- <<<Endofunctor>>>
- <<<Applicative functor>>>
- /*/
- <<<Applicative property>>>
- <<<Applicative function>>>
- <<<Special applicatives>>>
- <<<Monad>>>
- <<<Alternative type class>>>
- <<<Monoidal functor>>>
- =$>=
- <<<Multifunctor>>>
- <<<Hask category>>>
- <<<Morphism>>>
- <<<Set category>>>
- <<<Natural transformation>>>
- <<<Category dual>>>
- <<<Thin category>>>
- <<<Commuting diagram>>>
- <<<Universal construction>>>
- <<<Product>>>
- <<<Coproduct>>>
- <<<Free object>>>
- <<<Internal category>>>
- <<<Hom set>>>
- <<<Mag category>>>
- <<<Data type>>>
- /*/
- <<<Actual type>>>
- <<<Algebraic data type>>>
- <<<Cardinality>>>
- <<<Data constant>>>
- <<<Data constructor>>>
- <<<data declaration>>>
- <<<Dependent type>>>
- <<<Gen type>>>
- <<<Higher-kinded data type>>>
- <<<newtype declaration>>>
- <<<Principal type>>>
- <<<Product data type>>>
- <<<Proxy type>>>
- <<<Static typing>>>
- <<<Structural type>>>
- <<<Structural type system>>>
- <<<Sum data type>>>
- <<<Type alias>>>
- <<<Type class>>>
- <<<Type constant>>>
- <<<Type constructor>>>
- <<<type declaration>>>
- <<<Typed hole>>>
- <<<Type inference>>>
- <<<Type rank>>>
- <<<Type variable>>>
- <<<Unlifted type>>>
- <<<Linear type>>>
- <<<NonEmpty list data type>>>
- <<<Session type>>>
- <<<Binary tree>>>
- <<<Bottom value>>>
- <<<Bound>>>
- <<<Constructor>>>
- <<<Context>>>
- <<<Inhabit>>>
- <<<Maybe>>>
- <<<Expected type>>>
- <<<ADT>>>
- <<<Concrete type>>>
- <<<Type punning>>>
- <<<Kind>>>
- <<<IO>>>
- <<<Expression>>>
- <<<Function>>>
- /*/
- <<<Arity>>>
- <<<Bijection>>>
- <<<Combinator>>>
- <<<Function application>>>
- <<<Function body>>>
- <<<Function composition>>>
- <<<Function head>>>
- <<<Function range>>>
- <<<Higher-order function>>>
- <<<Injection>>>
- <<<Partial function>>>
- <<<Purity>>>
- <<<Pure function>>>
- <<<Sectioning>>>
- <<<Surjection>>>
- <<<Unsafe function>>>
- <<<Variadic>>>
- <<<Domain>>>
- <<<Codomain>>>
- <<<Open formula>>>
- <<<Recursion>>>
- <<<Free variable>>>
- <<<Closure>>>
- <<<Parameter>>>
- <<<Partial application>>>
- <<<Well-formed formula>>>
- <<<Homotopy>>>
- <<<Lambda calculus>>>
- <<<Operation>>>
- <<<Permutation>>>
- <<<Point-free>>>
- <<<Polymorphism>>>
- <<<Compositionality>>>
- <<<Referential transparency>>>
- <<<Semantics>>>
- <<<Operational semantics>>>
- <<<Denotational semantics>>>
- <<<Axiomatic semantics>>>
- <<<Content word>>>
- Ancient Greek and Latin prefixes
- <<<Set>>>
- <<<Testing>>>
- Logic
- Haskell structure
- /*/
- <<<Pattern match>>>
- <<<Smart constructor>>>
- <<<Level of code>>>
- <<<Orphan instance>>>
- <<<undefined>>>
- <<<Hierarchical module name>>>
- <<<Reserved word>>>
- <<<Haskell Language Report>>>
- <<<Haskell’>>>
- <<<Lense>>>
- <<<Pragma>>>
- <<<LANGUAGE pragma>>>
- <<<LANGUAGE option>>>
- /*/
- Useful by default
- <<<AllowAmbiguousTypes>>>
- <<<ApplicativeDo>>>
- <<<ConstrainedClassMethods>>>
- <<<CPP>>>
- <<<DeriveFunctor>>>
- <<<ExplicitForAll>>>
- <<<FlexibleContexts>>>
- <<<FlexibleInstances>>>
- <<<GeneralizedNewtypeDeriving>>>
- <<<ImplicitParams>>>
- <<<LambdaCase>>>
- <<<MultiParamTypeClasses>>>
- <<<MultiWayIf>>>
- <<<OverloadedStrings>>>
- <<<PartialTypeSignatures>>>
- <<<RankNTypes>>>
- <<<ScopedTypeVariables>>>
- <<<TupleSections>>>
- <<<TypeApplications>>>
- <<<TypeSynonymInstances>>>
- <<<UndecidableInstances>>>
- <<<ViewPatterns>>>
- <<<DatatypeContexts>>>
- <<<StandaloneKindSignatures>>>
- <<<PartialTypeSignatures>>>
- <<<TypeOperators>>>
- How to make a GHC LANGUAGE extension
- <<<LANGUAGE option>>>
- <<<LANGUAGE pragma>>>
- Computer science
- <<<Graph theory>>>
- <<<Tagless-final>>>
- <<<Prefix notation>>>
- Citation
- Good code
- <<<Good: Type aliasing>>>
- <<<Good: Type wideness>>>
- <<<Good: Print>>>
- <<<Good: Fold>>>
- <<<Good: Computation model>>>
- <<<Good: Make bottoms only local>>>
- <<<Good: Newtype wrap is ideally transparent for compiler and does not change performance>>>
- <<<Good: Instances of types/type classes must go with code you write>>>
- <<<Good: Functions can be abstracted as arguments>>>
- <<<Good: Infix operators can be bind to arguments>>>
- <<<Good: Arbitrary>>>
- <<<Good: Principle of Separation of concerns>>>
- <<<Good: Function composition>>>
- <<<Good: Point-free>>>
- <<<Good: Functor application>>>
- <<<Good: Parameter order>>>
- <<<Good: Applicative monoid>>>
- <<<Good: Creative process>>>
- Good: About operators
(<$ )
( **>)
(<* )
=(>> )= - <<<Good: About functions like {mapM, sequence}_>>>
- <<<Good: Guideliles>>>
- <<<Good: Use Typed holes to progress the code>>>
- <<<Good: Haskell allows infinite terms but not infinite types>>>
- <<<Good: Use type sysnonims to differ the information>>>
- Good: Use
Control.Monad.Except
instead of =Control.Monad.Error= - <<<Good: Monad OR Applicative>>>
- <<<Good: Linear type>>>
- Good: Exception vs Error
- <<<Good: Let vs. Where>>>
- <<<Good: RankNTypes>>>
- <<<Good: Handling orphan instance>>>
- <<<Good: Smart constructor>>>
- <<<Good: Thin category>>>
- <<<Good: Recursion>>>
- <<<Good: Monoid>>>
- <<<Good: Free monad>>>
- <<<Good: Use mostly where clauses>>>
- <<<Good: Where clause is in a scope with function parameters>>>
- <<<Good: Strong preference towards pattern matching over {head, tail, etc.} functions>>>
- <<<Good: Patternmatching is possible on monadic bind in do>>>
- <<<Good: Applicative vs Monad>>>
- <<<Good: StateT, ReaderT, WriterT>>>
- <<<Good: Working with MonadTrans and lift>>>
- <<<Good: Don’t mix Where and Let>>>
- <<<Good: Where vs. Let>>>
- <<<Good: The proper nature algorithm that models behaviour of many objects is computation heavy>>>
- <<<Good: In Haskell parameters bound by lambda declaration instantiate to only one concrete type>>>
- Good: Instance is a good structure to drew a type line
- <<<Good: MTL vs. Transformers>>>
- Good: Forget
error
, usefail
instead
- Bad code
- Useful functions to remember
- Tool
- Library
- Exceptions
- Exceptions - optionally pure extensible exceptions that are compatible with the mtl
- Safe-exceptions - safe, simple API equivalent to the underlying implementation in terms of power, encourages best practices minimizing the chances of getting the exception handling wrong.
- Enclosed-exceptions - capture exceptions from the enclosed computation, while reacting to asynchronous exceptions aimed at the calling thread.
- Memory management
- Parsers - megaparsec
- CLIs - optparse-applicative
- HTML - Lucid
- Web applications - Servant
- IO libraries
- JSON - aeson
- <<<Backpack>>>
- DSL
- Exceptions
- Draft
- Exception handling
- Ideal catching
- =Control.Exception.Safe= main sets of functions
- Clean-up of actions/resources
- Ideal model
- Universal exception type
- Individual exception types
- Abstract exception type
- Composit approach
- The changes in GHC 8.8
- Diversity in exceptions
- Exception handling strategies
- Asynchronous exception
- Monadic Error handling
- Constraints
- Monad transformers and their type classes
- Layering monad transformers
- Hoogle
- <<<ST-Trick monad>>>
- <<<Either>>>
- <<<Inverse>>>
- <<<Inversion>>>
- <<<Inverse function>>>
- <<<Inverse morphism>>>
- <<<Partial inverse>>>
- <<<PatternSynonyms>>>
- <<<GHC debug keys>>>
- <<<GHC optimize keys>>>
- <<<Computational trinitarianism>>>
- Techniques functional programming deals with the state
- Functions
- <<<Void>>>
- Intuitionistic logic
- <<<Principle of explosion>>>
- Universal property
- Yoneda lemma
- Monoidal category, functoriality of ADTs, Profunctors
- <<<Const functor>>>
- <<<Arrow in Haskell>>>
- Contravariant functor
- Profunctor
- Coerce
- Universal/Existential quantification
- Propagator
- Code technics
- Algorithm of the Hackage package release
- Form Git{Hub,Lab} pre-release
- Create git branch ~release x.x.x.x+1~
- Open-up
git diff <lastVer>..HEAD
on one side of the screen - Open
CHANGELOG.md
on the other side of the screen - Walk through diff and populate ~CHANGELOG.md~
- Check
cabal sdist
build passes - Think what new files can/should be included in
.cabal
~extra-source-files~ - Update
.cabal
~version:~ - Add a ~git tag <v>~
- ~git push –tags~
- (optional) (Remove git tag)
- Make a ~cabal sdist~
- Upload package candidate to Hackage
- (careful) Be fully ready when you upload package release to Hackage, since upload is idempotant
- (optional) If docs not posted on Hackage
- Is power set functor is a bifunctor
- IO
- <<<Lazy>>>
- <<<Traversable>>>
- <<<Fixed point>>>
- [[#-210][]]
- <<<Conway’s law>>>
- <<<F-algebra>>>
- Cabal artifacts
- ~Hpack~
- Exception handling
- Reference
- Giving back
SCHT: <2021-01-29 Fri>
\arabicfont{الجبر} al-jabr assemble parts
A system of parts based on given axioms (properties) and operations on them.
\additional
Additional meanings:
- Algebra - a set with its algebraic structure.
- Abstract algebra - the study of number systems and operations within them.
- Algebra - vector space over a field with a multiplication.
- In Haskell mosr often used as substitute to “particular implementation” on top of some (considered well-known or basis to the code by the code author) theory/principle/abstraction mechanism.
<<<Algebras>>>
Composite from simple parts.
Also: Algebraic data type.
SCHT: <2020-12-28 Mon>
* includes axioms that must be satisfied and operations on the underlying (or “carrier”) set.
An underlying set with * on top of it also called “an algebra”.
* include groups, rings, fields, and lattices. More complex structures can be defined by introducing multiple operations, different underlying sets, or by altering the defining axioms. Examples of more complex * can be many modules, algebras and other vector spaces, and any variations that the definition includes.
Closure | Associativity | Identity | Invertability | Commutativity | Distributive | |
---|---|---|---|---|---|---|
Semigroupoid | \check | |||||
Small Category | \check | \check | ||||
Groupoid | \check | \check | \check | |||
Magma | \check | |||||
Quasigroup | \check | \check | ||||
Loop | \check | \check | \check | |||
Semigroup | \check | \check | ||||
Inverse Semigroup | \check | \check | \check | |||
Monoid | \check | \check | \check | |||
Group | \check | \check | \check | \check | ||
Abelian group | \check | \check | \check | \check | \check | |
Non-unital ring (rng) | \check + × | \check + × | \check + | \check + | \check + | \check |
Semiring (rig) | \check + × | \check + × | \check + × | \check × | \check + | \check |
Ring | \check + × | \check + × | \check + × | \check + × | \check + | \check |
<<<Algebraic structures>>>
SCHT: <2020-08-07 Fri>
Any non-constant single-variable polynomial with complex coefficients has at least one complex root.
From this definition follows property that the field of complex numbers is algebraically closed.
Set with a binary operation which form a closure.
SCHT: <2020-10-01 Thu>
Magma with associative property of operation.
Defined in Haskell as:
class Semigroup a where
(<>) :: a -> a -> a
<<<Semigroups>>>
SCHT: <2020-08-06 Thu>
Semigroup with identity element.
Ideal ground for any accumulation class.
class Semigroup m => Monoid m where
mempty :: m
mconcat :: [m] -> m
mconcat = foldr mappend mempty
More generally in category theory terms:
* - the object \( M \) equipped with two arrows:
\( μ: \ M \ ⊗ \ M \ → M \) called multiplication or product, or tenzor product. \( η: \ I \ → \ M \) called unit,
so \((M, \ μ, \ η )\). By its definition category (lets call it \( \mathb{C} \) should have \( ⊗ \) and \( I \). Where \( ⊗: \ \mathb{C} \ × \ \mathb{C} \ → \ \mathb{C} \) is any operation that combines objects and stays (closed) inside category, so it may be even already category given operation of arrow composition. And \( I \) is an identity object of \( ⊗ \) operation.
Category that has one object - always a free monoid (from definition of “Category” - composition, and there is only one object so it is always also the identity object).
For example to represent the whole non-negative integers with the one object and morphism “\( 1 \)” is absolutely enough, composition operation is “\( + \)”.
import Data.Monoid
do
show (mempty :: Num a => Sum a)
-- "Sum {getSum = 0}"
show $ Sum 1
-- "Sum {getSum = 1}"
show $ (Sum 1) <> (Sum 1) <> (Sum 1)
-- "Sum {getSum = 3}"
-- ...
And backwards connection. Any monoidal category can be isomorphically transformed into one-object bicategory, thou explaining or proving it is out of the current scope.
Any monad is equivalent up to isomorphism to monoid.
3.1.3.3.1.2.1 *<<<Monoidal>>> <<<Monoids>>>
3.1.3.3.1.2.2 <<<Monoid properties>>>3.1.3.3.1.2.2.1 <<<Monoid left identity property>>> SCHT: <2020-10-11 Sun>mempty <> x = x
x <> mempty = x
x <> mempty = x (y <> z) = (x <> y) <> z
mconcat = foldr (mempty <>)
Everything associative can be mappend
.
Operation that forms structure has commutativity property: \( x ˆ y = y ˆ x \)
Opens a big abilities in concurrent and distributed processing.
3.1.3.3.1.2.3.1 *<<<Abelian monoid>>>
3.1.3.3.1.2.4 <<<Group>>> SCHT: <2020-07-04 Sat>Monoid that has inverse for every element.
3.1.3.3.1.2.4.1 *<<<Groups>>>
3.1.3.3.1.2.4.2 <<<Commutative group>>> SCHT: <2020-05-27 Wed>Commutative monoid that is a group.
3.1.3.3.1.2.4.2.1 *<<<Abelian group>>>
3.1.3.3.1.2.4.2.2 <<<Ring>>> SCHT: <2020-06-17 Wed>Commutative group under + & monoid under ×, + × connected by distributive property.
- and × are generalized binary operations of addition and multiplication. × has no requirement for commutativity.
Example: set of same size square matricies of numbers with matrix operations form a ring.
3.1.3.3.1.2.4.2.2.1 *<<<Rings>>>
System for integers where numbers wrap around the certain values (single - modulus, plural - moduli).
Example - 12-hour clock.
<<<Clock arithmetic>>>
SCHT: <2020-08-06 Thu>
Special numbers where arithmetic wraps around in modular arithmetic.
<<<Moduli>>> - plural.
SCHT: <2020-06-17 Wed>
Category \( \mathcal{C} \) consists of the basis:
Primitives:
- Objects - \( a\mathcal{C} \). A node. Object of some type. Often sets, than it is Set category.
- Arrows - \( {(a,b)}\mathcal{C} \) (AKA morphisms mappings).
- Arrow (morphism) composition - binary operation: \( {(a, b)}\mathcal{C} ˆ {(b, c)}\mathcal{C} ≡ {(a, c)}\mathcal{C} \ | \ ∀ a, b, c ∈ \mathcal{C} \) AKA principle of compositionality for arrows.
Properties (or axioms):
- Associativity of morphisms: \( {h} ˆ ({g} ˆ {f}) ≡ ({h} ˆ {g}) ˆ {f} \ \ | \ \ {f}a → b, {g}b → c, {h}c → d \)
- Every object has (two-sided) identity morphism (& in fact - exactly one): \( {1}_x ˆ {f}a → x ≡ {f}a → x, \ \ {g}x → b ˆ {1_x} ≡ {g}x → b \ \ | \ \ ∀ x \ ∃ {1}x, ∀ {f}a → x, ∀ {g}x → b \)
- Principle of compositionality.
From these axioms, can be proven that there is exactly one identity morphism for every object.
Object and morphism are complete abstractions for anything. In majority of cases under object is a state and morphism is a change.
<<<Category>>> <<<Categories>>>
SCHT: <2020-07-11 Sat>
Generalised category for homological algebra (having a possibility of basic constructions and techniques for it).
Category which:
- has a zero object,
- has all binary biproducts,
- has all kernel’s and cokernels,
- (it has all pullbacks and pushouts)
- all monomorphism’s and epimorphism’s are normal.
Abelian category is a stable structure; for example it is regular and satisfy the snake lemma. The class of Abelian categories is closed under several categorical constructions.
There is notion of Abelian monoid (AKS Commutative monoid) and Abelian group (Commutative group).
Basic examples of *:
- category of Abelian groups
- category of modules over a ring.
* are widely used in algebra, algebraic geometry, and topology.
* has many constructions like in categories of modules:
- kernels
- exact sequences
- commutative diagrams
* has disadvantage over category of modules. Objects do not necessarily have elements that can be manipulated directly, so traditional definitions do not work. Methods must be supplied that allow definition and manipulation of objects without the use of elements.
<<<Abelian categories>>>
SCHT: <2020-07-17 Fri>
Axiom of Category.
<<<Composable>>> <<<Compositions>>>
From the name, in this Category:
- objects of \( End \) are Endofunctors \( E\mathcal{C → C} \)
- morphisms are natural transformations between endofunctors
SCHT: <2020-07-21 Tue>
* full translation (map) of one category into another. Translating objects and morphisms (so as an input can take morphism or object of the source category).
“Full translation” means every part gets represented in some shape or form, but at all does not means ideal translation. For example, all categories can be translated into (mapped onto) a single object monoidal category. * - forgetful - discards part of the structure. * - faithful - gives unique isomorphic (bijective) preservation of all source morphisms (injective on Hom-sets). * - full - translation of morphisms fully covers all the morphisms between according objecs in the target categoty (functor analog of epimorphism).
For Haskell Functor type class or fmap
- see Power set functor.
Definition (axiomatic properties):
Functor
:
- \( ∀ a\mathcal{C} \ : \ ∃! F\mathcal{C → D}(a) \) - every source object is mapped to some object in the target category.
- \( ∀ \overrightarrow{(a, b)}\mathcal{C} \ : \ ∃! \overrightarrow{(F\mathcal{C → D}(a),F\mathcal{C → D}(b))}\mathcal{D }\) - every source morphism is mapped inside target to some morphism between corresponding objects.
From those two tautologically goes:
- \( ∀ {x\mathcal{C}}, y=\overrightarrow{f}\mathcal{C}(x), ∀ \overrightarrow{g}\mathcal{C}(y) \ : \ F\mathcal{C → D}(\overrightarrow{g}\mathcal{C} ˆ \overrightarrow{f}\mathcal{C}) = F\mathcal{C → D}(\overrightarrow{g}\mathcal{C}) ˆ F\mathcal{C → D}(\overrightarrow{f}\mathcal{C})\) - every composition in \( \mathcal{C} \) translates as a composition of according morphisms in \( \mathcal{D} \), in other words - composition translates directly.
So, the composition of functors equal to one functor with composition of all morphisms. This process called functor fusion.
In Haskell Hask functor axioms have a form:
fmap f id = id f :: (f -> f) -- All objects (f) in Hask can be mapped to Hask.
fmap id id :: (a -> a) -- fmap can map objects. This is constructed identity endofunctor on Hask.
fmap id :: (f a -> f a) -- fmap can map objects, algebraic also (which includes funcitons (morphisms))
(\ x -> fmap x id) :: (a -> b) -> (a -> b)
(flip fmap id) :: (a -> b) -> (a -> b) -- & functions (morphisms) just as well, polymorphism means functions are also simple type objects, and in Haskell functions are first class
-- This is enough to prove fmap is a functor, composition property derives from this two
In Haskell type functor axioms have a form:
fmap id = id
fmap (f . g) = fmap f . fmap g
-- OR free-forming functor laws more expicitly:
(fmap id) a = id a -- Remaps all source objects (a) to object, in identity case maps all a to a
(fmap f) a = (f a) -- Remaps all source objects using a specialized functor by declaring a the funciton that does remapping of objects
(fmap hof@((a -> b) -> c)) fun@(a -> b) = (hof fun) = (a -> b) -> c -- Because of polymorphicity - in Haskell morphisms are also can be objects for Hask category - `fmap` instantiated functor translates not only objects, but all morphisms to morphisms as well.
(fmap (a -> b)) anything = ((a -> b) anything) -- On Hask subcategory (f x), this is an endofunctor: f a -> f b.
(fmap f) . (fmap g) = (fmap $ f . g) -- Composition law
Since * is 1-1 mapping of initial objects - it is a memoizable dictionary with cardinality of initial objects. Also in Hask category functors are obviously endofunctors \therefore they are special kinds of containers for the parametric values (AKA product type). In Haskell product type * are endofunctors from polymorphic type into a functor wrapper of a polymorphic type.
* translates in one direction, and does not provide algorythm of reversing itself or retriving the parametric value.
<<<Functors>>> <<<Functorial>>> - something that has functor properties, and so also is a functor.
SCHT: <2021-06-03 Thu>
\( \mathcal{PS → P(S)} \)
* - functor from set \( S \) to its power set \( \mathcal{P}(S) \).
In Haskell terms - a power set functor additionally accepts function parametrisation.
Functor type class in Haskell defines a * as fmap
in a form of bifunctor. It allows to do function application inside type structure layers (denoted \( f \) or \( m \)). IO is also such structure.
Power set is unique to the set, * is unique to the data type (to the category also).
Any endofunctor embodies into *. It is easily seen from Haskell definition - that the * is the polymorphic generalization over any endofunctor in a category.
Application of a function to * gives a particular endofunctor (see Hask category).
class Functor f where
fmap :: (a -> b) -> f a -> f b
Functor instance must be of kind ( * -> * )
, so instance for higher-kinded data type must be applied until this kind.
Composed * can lift functions through any layers of structures that belong to Functor type class.
* can be used to filter-out the structure through strucure composition, for example - composition with error cases (Nothing & Left cases) in Maybe, Either and related types.
<<<fmap>>> <<<Functor type class>>>
SCHT: <2020-06-03 Wed>
Type instance of functor should abide this properties:
<<<Functor properties>>>
SCHT: <2020-08-17 Mon>
Functor translates object & its identity morphism to target object & its identity morphism.
fmap id == id
Full transparency of composition translation. So order of composition and translation does not metter, the result is always the same.
fmap (f . g) == fmap f . fmap g
Including cases: a) translate everything one-by-one and assemble at destination category. b) assemble everything in source cetegory and translate in one go once.
Composing in source category and translating at once - is a much-much more effective computation (known as “functor <<<fusion”>>>).
SCHT: <2020-09-18 Fri>
fmap :: (a -> b) -> (f a -> f b)
Functor takes function a -> b
and returns a function f a -> f b
this is called lifting a function.
Lift does a function application through the data structure.
<<<Lifting>>>
SCHT: <2020-09-14 Mon>
Since:
- \( ∀ e ∈ S : \ ∃ \{e\} \, ∈ \, {\mathcal{P}(S)} \ \vDash \ \ ∀ e ∈ S : \ ∃ (e → \{e\}) ≡ unit \)
- \( ∀ \mathcal{P}(S) : \ \mathcal{P}(S) ∈ \mathcal{P}(S) \ \vDash \ \ ∀ \mathcal{P}(S) : \ ∃ (\mathcal{P}(\mathcal{P}(S)) → \mathcal{P}(S)) ≡ join \)
Functor that forgets part or all of what defines structure in domain category. \( F\mathbf {Grp → \mathbf {Set}} \) that translates groups into their underlying sets. Constant functor is another example.
<<<Forgetful>>>
SCHT: <2020-12-22 Tue>
Maps all category to itself. All objects and morphisms to themselves.
Denotation: \( 1\mathcal{C → C} \)
SCHT: <2020-07-07 Tue>
Is a functor which source (domain) and target (codomain) are the same category.
\( F\mathcal{C → C}, E\mathcal{C → C} \)
<<<Endofunctors>>>
SCHT: <2020-09-02 Wed>
* - Computer science term. Category theory name - lax monoidal functor. And in category \( Set \), and so in category \( Hask \) all applicatives and monads are strong (have tensorial strength).
* - sequences functorial computations (plain functors can’t).
(<*>) :: f (a -> b) -> f a -> f b
Requires Functor to exist. Requires Monoidal structure.
Has monoidal structure rules, separated form function application inside structure.
Data type can have several applicative implementations.
Standard definition:
class Functor f => Applicative f
where
(<*>) :: f (a -> b) -> f a -> f b
pure :: a -> f a
pure
- if a functor, identity Kleisli arrow, natural transformation.
Composition of * always produces *. (* are closed unders composition).
Control.Monad
has an old function ap
that is old implementation of <*>
:
ap :: Monad m => m (a -> b) -> m a -> m b
<<<Applicative>>> <<<Applicatives>>> <<<Applicative functors>>>
<<<Applicative properties>>>
SCHT: <2020-09-07 Mon>
pure id <*> v = v
SCHT: <2020-07-22 Wed>
To compose functions contained within applicatives is the same as using normal function composition inside of an applicative, aka function composition works regularly.
pure (.) <*> u <*> v <*> w = u <*> (v <*> w)
Explanation:
pure (.) <*> Right (+20) ==
Right ((.) (+20))
pure (.) <*> Right (+20) <*> Right (+10) ==
(Right <> Right) ((.) (+20) (+10)) ==
(Right <> Right) (+20 . +10) ==
Right (+30)
pure (.) <*> Right (+20) <*> Right (+10) <*> Right 5 ==
Right ((.) (+20) (+10) (5)) ==
Right ((+20 . +10) (5)) ==
Right ((+30) 5) ==
Right 35
& also:
Right (+20) <*> (Right (+10) <*> Right (5)) ==
Right (+20) <*> ((Right <> Right) (+10) (5)) ==
(Right <> Right <> Right) ((+20) (15)) ==
Right 35
Aka, {<*>, pure}
represent {<>, ' ' (function application)}
at the same time. How applicative operators applied inside of the Haskell expression - provides information how to compose the applicative structure as a monoid, and contents as a function application. Rules they apply by are just as they would be if to remove applicative operators and {applicative structures OR context}
(depenting on what to stay).
pure (.) <*> au <*> bv <*> cw = au <*> (bv <*> cw)
-- Contents applies:
(.) u v w = u (v w)
pure (.) <*> au <*> bv <*> cw = au <*> (bv <*> cw)
-- Applicative structure applies:
pure <> a <> b <> c = a <> (b <> c)
That is the essence of the law.
SCHT: <2020-09-18 Fri>
Internal function application doesn’t change the structure around values.
pure f <*> pure x = pure (f x)
SCHT: <2020-06-27 Sat>
On condition that internal order of evaluation is preserved - order of operands is not relevant.
u <*> pure y = pure ($ y) <*> u
This shows that because <*>
applies function to the argument - the order is important.
In other words - it is not commutative. And to turn the application order in <*>
the argument needs to be demoted ($
).
It works so:
uf <*> pure y
(u <> pure) (f y)
pure ($ y) <*> uf -- `$` is infix operator, so it binds `y` as second argument: `(\ f y -> f $ y)`
pure (($) y) <*> uf
(pure <> u) (f $ y)
Essentially a fmap.
:type liftA
liftA :: Applicative f => (a -> b) -> f a -> f b
Lifts function into applicative function.
3.2.5.6.3.1.2 <<<liftA2>>> SCHT: <2020-09-18 Fri>Lifts binary function across two Applicative functors.
liftA2 :: Applicative f => (a -> b -> c) -> f a -> f b -> f c
liftA2 f x y == pure f <*> x <*> y
liftA2 (<*>)
is an applicative that lifts a binary operation over the two layers (2x2). Pretty useful to remember it.
liftA2 :: ( a -> b -> c ) -> f a -> f b -> f c
<*> :: (f (a -> b) -> f a -> f b)
liftA2 (<*>) :: f1 (f2 (a -> b)) -> f1 (f2 a) -> f1 (f2 b)
liftA2 (<*>)
3-layer version.
liftA2 3-parameter version.
liftA3 f x y z == pure f <*> x <*> y <*> z
when :: Applicative f => Bool -> f () -> f ()
Only when True
- perform an applicative computation.
unless :: Applicative f => Bool -> f () -> f ()
Only when False
- perform an applicative computation.
SCHT: <2020-06-23 Tue>
-- Applicative f =>
-- f ~ Identity
type Id = Identity
instance Applicative Id
where
pure :: a -> Id a
(<*>) :: Id (a -> b) -> Id a -> Id b
mkId = Identity
xs = [1, 2, 3]
const <$> mkId xs <*> mkId xs'
-- [1,2,3]
SCHT: <2020-05-02 Sat>
It holds only to one value. The function does not exist and last parameter is a phantom.
-- Applicative f =>
-- f ~ Constant e
type C = Constant
instance Applicative C
where
pure :: a -> C e a
(<*>) :: C e (a -> b) -> C e a -> C e b
SCHT: <2020-10-16 Fri>
“There also can be no function at all.”
If function might not exist - embed f
in Maybe structure, and use Maybe applicative.
-- f ~ Maybe
type M = Maybe
pure :: a -> M a
(<*>) :: M (a -> b) -> M a -> M b
pure
is Right
.
Defaults to Left
.
And if there is two Left
’s - to Left of the first argument.
SCHT: <2020-12-26 Sat>
The Validation data type isomorphic to Either, but has accumulative Applicative on the Left side.
Validation data type does not have a monad implemented.
For Either monad monad has simple implementation: Left
case drops computation and returns Left
value.
Monad needs to process the result of computation - for Validation - it requires to be able to process all Left
error statement cases for Validation, it is or non-terminaring Monad or one which is impossible to implement in polymorphic way with Validation.
SCHT: <2021-03-17 Wed>
\textgreek{μόνος} monos sole
\textgreek{μονάδα} monáda unit
In loose terms, * - is an ability built over structures that allows to compose functions that produce that structures.
Since it is possible to express unpure functions with equivalent pure functions that produce a structure, * become widely used in Haskell for those cases also. * with lazy evaluation also allows controll over the continuation of calculations by early terminations.
* - lax monoid in endofunctor category, that relies on \( η \) (unit) and \( μ \) (join) natural transformations to form an equivalent of identity.
Monad on \( \mathcal{C} \) is \( \{E\mathcal{C → C}, \, η, \, μ\} \):
- \( E\mathcal{C → C} \) - is an endofunctor
- two natural transformations, \( 1^c → E \) and \( E ˆ E → E \):
- \( η1^{\mathcal{C} → E} = {unit}Identity → E(x) = f x → E(x)(x) \)
- \( μ(E ˆ E) → E = {join}(E ˆ E) → (Identity ˆ E)(x) = | y = E(x) | = fE (y) → y(y) \)
where:
- \( \mathcal{C} \) is a category
- \( 1\mathcal{C} \) denotes the \( \mathcal{C} \) identity functor
- \( (E ˆ E) \) - endofunctor \( \mathcal{C → C} \)
Definition with \( \{E\mathcal{C → C}, \, η, \, μ\} \) (in Hask: (\( \{e \, :: \, f \, a \, → \, f \, b, \ pure, \ join\} \))) - is classic categorical, in Haskell minimal complete definition is \( \{fmap, \, pure, \, (>>=)\} \).
While \( T \) is mode classical Category theory notation, we used the \( E ≡ T \) substitution for purposes of notation being more understandable.
If there is a structure \( S \), and a way of taking object \( x \) into \( S \) and a way of collapsing \( S ˆ S \) - there probably a monad.
Monad structure:
\begin{tikzcd}
& & {} \arrow[d, “η”, Rightarrow] & &
C \arrow[rrrr, “Id”, bend left=49] \arrow[rrrr, “E”] \arrow[rrrr, “E2”, bend right=49] & & {} & & C \
& & {} \arrow[u, “μ”, Rightarrow]
\end{tikzcd}
Mostly monads used for sequencing actions (computations) (that looks like imperative programming), with ability to dependend on previous chains. Note if monad is commutative - it does not order actions.
Monad can shorten/terminate sequence of computations. It is implemented inside Monad instance. For example Maybe monad on Nothing drops chain of computation and returns Nothing.
* inherits the Applicative instance methods:
import Control.Monad (ap)
return == pure
ap == (<*>) -- + Monad requirement
Math | Meaning | Cat/Fctr | \( X ∈ C \) | Type | Haskell |
---|---|---|---|---|---|
\( Id \) | endofunctor “Id” | \( C → C \) | \( X → Id (X) \) | \( a → a \) | id |
\( E \) | endofunctor “monad” | \( C → C \) | \( X → E (X) \) | \( m \ a → m \ b \) | fmap |
\( η \) | natural transformation “unit” | \( Id → E \) | \( Id (X) → E (X) \) | \( a → m \ a \) | pure |
\( μ \) | natural transformation “multiplication” | \( E ˆ E → E \) | \( E (E(X)) → E (X) \) | \( m \ (m \ a) → m \ a \) | join |
Internals of Monad are Haskell data types, and as such - they can be consumed any number of times.
Contrary to applicative functors composition of which always produces applicative, composition of monads does not always results in monad. (Monads are not closed under composition).
<<<Monads>>> <<<Monadic>>>
SCHT: <2021-05-15 Sat>
Monad corresponds to functor properties & applicative properties and additionally:
3.2.5.6.5.2.1 * <<<Monad properties>>>3.2.5.6.5.2.2 <<<Monad left identity property>>> SCHT: <2020-08-20 Thu>f <=< pure == f
Explanation:
(=<<)
:: Monad f
=> (a -> f b) -> f a -> f b
(=<<) f (pure x) == f x
Rule that >>=
must get first argument structure internals and apply to the function that is the second argument.
Diagram on category level:
\begin{tikzcd}
& & {} \arrow[dd, “η”, Rightarrow] & & & & {} \arrow[dd, “I”, Rightarrow] & &
C \arrow[rrrr, “Id”, bend left=49] \arrow[rrrr, “T”, bend right=49] \arrow[rrrrrrrr, “T”, bend right=75] & & & & C \arrow[rrrr, “T”, bend left=49] \arrow[rrrr, “T”, bend right=49] & & & & C \
& & {} & & {} \arrow[dd, “μ”, Rightarrow] & & {} & & \
& & & & & & & & \
& & & & {}
\end{tikzcd}
Diagram on endomorphism level:
\begin{tikzcd}
Id ˆ T \arrow[rr, “η ˆ I”] \arrow[rrdd, no head, Rightarrow] & & T2 \arrow[dd, “μ”]
& & \
& & T
\end{tikzcd}
f >>= pure == f
Explanation:
>>= :: Monad f => f a -> (a -> f b) -> f b
f >>= pure == f
AKA it is a tacit description of a monad bind as endofunctor.
Diagram on category level:
\begin{tikzcd}
& & {} \arrow[dd, “I”, Rightarrow] & & & & {} \arrow[dd, “η”, Rightarrow] & &
C \arrow[rrrr, “T”, bend left=49] \arrow[rrrr, “T”, bend right=49] \arrow[rrrrrrrr, “T”, bend right=75] & & & & C \arrow[rrrr, “Id”, bend left=49] \arrow[rrrr, “T”, bend right=49] & & & & C \
& & {} & & {} \arrow[dd, “μ”, Rightarrow] & & {} & & \
& & & & & & & & \
& & & & {}
\end{tikzcd}
Diagram on endomorphism level:
\begin{tikzcd}
T2 \arrow[dd, “μ”] & & T ˆ Id \arrow[ll, “I ˆ η”] \arrow[lldd, no head, Rightarrow]
& & \
T
\end{tikzcd}
join (join (m m) m) == join (m join (m m))
(m >>= f) >>= g == m >>= (\ x -> f x >>= g)
In diagram form:
Category level:
\begin{tikzcd}
& & {} \arrow[dd, “I”, Rightarrow] & & & & {} \arrow[dd, “μ”, Rightarrow] & &
C \arrow[rrrr, “T”, bend left=49] \arrow[rrrr, “T”, bend right=49] \arrow[rrrrrrrr, “T”, bend right=75] & & & & C \arrow[rrrr, “T2”, bend left=49] \arrow[rrrr, “T”, bend right=49] & & & & C \
& & {} & & {} \arrow[dd, “μ”, Rightarrow] & & {} & & \
& & & & & & & & \
& & & & {}
\end{tikzcd}
is \( = \) to:
\begin{tikzcd}
& & {} \arrow[dd, “μ”, Rightarrow] & & & & {} \arrow[dd, “I”, Rightarrow] & &
C \arrow[rrrr, “T2”, bend left=49] \arrow[rrrr, “T”, bend right=49] \arrow[rrrrrrrr, “T”, bend right=75] & & & & C \arrow[rrrr, “T”, bend left=49] \arrow[rrrr, “T”, bend right=49] & & & & C \
& & {} & & {} \arrow[dd, “μ”, Rightarrow] & & {} & & \
& & & & & & & & \
& & & & {}
\end{tikzcd}
So, \( μ ˆ (μ ˆ I) = μ ˆ (I ˆ μ) \)
Endomorphism level:
\begin{tikzcd}
& & T3 \arrow[dd, “μ ˆ I”, bend right=49] \arrow[dd, “I ˆ μ”, bend left=49] & &
& & & & \
& & T2 \arrow[dd, “μ”] & & \
& & & & \
& & T
\end{tikzcd}
class Applicative m => Monad m where
(>>=) :: m a -> (a -> m b) -> m b
(>>) :: m a -> m b -> m b
return :: a -> m a
Is a monoid over monad, with additional rules. The precise set of rules (properties) not agreed upon. Class instances obey monoid & left zero rules, some additionally obey left catch and others left distribution.
* currently reforms (MonadPlus reform proposal) into several smaller and strictly defined type classes.
Subclass of an Alternative.
3.2.5.6.5.3.1.1 *<<<Monadplus>>>
<$> :: Functor f => (a -> b) -> f a -> f b
<*> :: Applicative f => f (a -> b) -> f a -> f b
=<< :: Monad f => (a -> f b) -> f a -> f b
pure
& join
are Natural transformations for the fmap
.
return == pure
Nonstrict.
3.2.5.6.5.5.2 <<<Join function>>>join :: Monad m => m (m a) -> m a
Generalized concat
.
Kleisli composition that flattens two layers of structure into one.
The way to express ordering in lambda calculus is to nest.
3.2.5.6.5.5.2.1 *<<<join>>>
3.2.5.6.5.5.2.2 join . fmap == (=<<)<$> :: Monad f => (a -> f b) -> f a -> f (f b)
join :: Monad f => f (f a) -> f a
join $ f <$> a :: Monad f => (a -> f b) -> f a -> f b
=<< :: Monad f => (a -> f b) -> f a -> f b
=<< :: Monad f => (a -> f b) -> f a -> f b
join $ f <$> a :: Monad f => (a -> f b) -> f a -> f b
Nonstrict.
The most ubiqutous way to =<<
something is to use Lambda function:
(\ name -> putStrLn "age pls:") =<< getLine
Also a neet way is to bundle and handle Monad - is to bundle it with bind, and leave applied partially. And use that partial bundle as a function - every evaluation of the function would trigger evaluation of internal Monad structure. Thumbs up.
printOneOf :: Bool -> IO ()
printOneOf False = putStr "1"
printOneOf True = putStr "2"
quant :: (Bool -> IO b) -> IO b
quant = (>>=) (randomRIO (False, True))
recursePrintOneOf :: Monad m => (t -> m a) -> t -> m b
recursePrintOneOf f x = (f x) >> (recursePrintOneOf f x)
main :: IO ()
main = recursePrintOneOf (quant) $ printOneOf
<<<Monadic extend>>> <<<Monadic bind>>> <<<Monad bind>>> <<<Binder>>>
(>>=)
>>=
(=<<)
=<<
(>> ) \equiv ( *>)
:
SCHT: <2020-06-09 Tue>
Sequencing operator, analog to the semicolon (or newline) in imperative languages. Discard value result of the action, sequentially add next (compose with) next action. Applicative has a similar operator.
(*>)
:: Applicative f
=> f a -> f b -> f b
(>>)
:: Monad m
=> m a -> m b -> m b
sequenceA
:: ( Traversable t
, Applicative m
)
=> t (m a)
-> m (t a)
Sequence gets the traversable of monadic computations and swaps it into monad computation of taverse. In the result the collection of monadic computations turns into one long monadic computation on traverse of data.
If some step of this long computation fails - monad fails.
traverse
:: ( Traversable t
, Applicative f
)
=> ( a
-> f b
)
-> t a
-> f (t b)
mapM
gets the AMB function, then takes traversable data. Then applies AMB function to traversable data, and returns converted monadic traversable data.
foldM :: (Foldable t, Monad m) => (b -> a -> m b) -> b -> t a -> m b
foldl :: Foldable t => (b -> a -> b) -> b -> t a -> b
* is a monadic foldl
.
b
is initial comulative value, m b
is a comulative bank.
Right folding achieved by reversing the input list.
filterM :: Applicative m => (a -> m Bool) -> [a] -> m [a]
filter :: (a -> Bool) -> [a] -> [a]
Take Boolean monadic computation, filter the list by it.
zipWithM :: Applicative m => (a -> b -> m c) -> [a] -> [b] -> m [c]
zipWith :: (a -> b -> c) -> [a] -> [b] -> [c]
Take monadic combine function and combine two lists with it.
msum :: (Foldable t, MonadPlus m) => t (m a) -> m a
sum :: (Foldable t, Num a) => t a -> a
Essentially a fmap.
liftM :: Monad m => (a -> b) -> m a -> m b
Lifts a function into monadic equivalent.
3.2.5.6.5.5.6.2 <<<liftM2>>>Monadic liftA2.
liftM2 :: Monad m => (a -> b -> c) -> m a -> m a -> m c
Lifts binary function into monadic equivalent.
SCHT: <2020-05-14 Thu>
Category \( \mathcal{C} \) comonad is a monad of opposite category \( \mathcal{C}op \).
SCHT: <2020-05-01 Fri>
Morphism that while doing computation also adds monadic-able structure.
a -> m b
<<<Kleisli arrows>>> <<<Kleisli morphism>>> <<<Kleisli morphisms>>>
Composition of Kleisli arrows.
(<=<) :: Monad m => (b -> m c) -> (a -> m b) -> a -> m c infixr 1
;; compare
(.) :: (b -> c ) -> (a -> b ) -> a -> c
Often used left-to-right version:
(>=>) :: Monad m => (a -> m b) -> (b -> m c) -> a -> m c
;; compare
(>>=) :: Monad m => m a -> (a -> m b) -> m b
Which allows to replace monadic bind chain with Kleisli composition.
f1 arg >>= f2 >>= f3
==
f1 >=> f2 >=> f3 $ arg
==
f3 <=< f2 <=< f1 $ arg
SCHT: <2020-05-29 Fri>
Category \( \mathcal{C} \), \( 〈E, \overrightarrow{η}, \overrightarrow{μ}〉 \) monad over \( \mathcal{C} \).
Kleisli category \( \mathcal{C}T \) of \( \mathcal{C} \):
\( \mathrm{Obj}(\mathcal{C}T) \ = \ \mathrm{Obj}(\mathcal{C}) \) \( \mathrm{Hom}\mathcal{CT}(x,y) \ = \ \mathrm{Hom}\mathcal{C}(x,E(y)) \)
3.2.5.6.5.10.1 <<<Identity monad>>> SCHT: <2020-05-01 Fri>Wraps data in the Identity constructor.
Useful: Creates monads from monad transformers.
Bind: Applies internal value to the bound function.
Code: (see: coerce)
newtype Identity a = Identity { runIdentity :: a }
instance Functor Identity where
fmap = coerce
instance Applicative Identity where
pure = Identity
(<*>) = coerce
instance Monad Identity where
m >>= k = k (runIdentity m)
Example:
-- derive the State monad using the StateT monad transformer
type State s a = StateT s Identity a
Something that may not be or not return a result. Any lookups into the real world, database querries.
Bind: Nothing
input gives Nothing
output, Just x
input uses x
as input to the bound function.
When some computation results in Nothing - drops the chain of computations and returns Nothing.
Zero: Nothing Plus: result in first occurence of Just else Nothing.
Code:
data Maybe a = Nothing | Just a
instance Monad Maybe where
return = Just
fail = Nothing
Nothing >>= _ = Nothing
(Just x) >>= f = f x
instance MonadPlus Maybe where
mzero = Nothing
Nothing `mplus` x = x
x `mplus` _ = x
Example: Given 3 dictionaries:
- Full names to email addresses,
- Nicknames to email addresses,
- Email addresses to email preferences.
Create a function that finds a person’s email preferences based on either a full name or a nickname.
data MailPref = HTML | Plain
data MailSystem = ...
getMailPrefs :: MailSystem -> String -> Maybe MailPref
getMailPrefs sys name =
do let nameDB = fullNameDB sys
nickDB = nickNameDB sys
prefDB = prefsDB sys
addr <- (lookup name nameDB) `mplus` (lookup name nickDB)
lookup addr prefDB
When computation results in Left
- drops other computations & returns the recieved Left
.
Someting that can fail, throw exceptions.
The failure process records the description of a failure. Bind function uses successful values as input to the bound function, and passes failure information on without executing the bound function.
Useful: Composing functions that can fail. Handle exceptions, crate error handling structure.
Zero: empty error. Plus: if first argument failed then execute second argument.
3.2.5.6.5.10.5 <<<List monad>>>Computations which may return 0 or more possible results.
Bind: The bound function is applied to all possible values in the input list and the resulting lists are concatenated into list of all possible results.
Useful: Building computations from sequences of non-deterministic operations.
Zero: [] Plus: (++)
3.2.5.6.5.10.5.1 *<<<[] monad>>>
3.2.5.6.5.10.6 <<<Reader monad>>> SCHT: <2020-07-20 Mon>Creates a read-only shared environment for computations.
The pure
function ignores the environment, while >>= passes the inherited environment to both subcomputations.
Today it is defined though ReaderT transformer:
type Reader r = ReaderT r Identity -- equivalent to ((->) e), (e ->)
Old definition was:
newtype Reader e a = Reader { runReader :: (e -> a) }
For (e ->)
:
- Functor is
(.)
fmap :: (b -> c) -> (a -> b) -> a -> c
fmap = (.)
- Applicative:
pure
isconst
pure :: a -> b -> a
pure x _ = x
(<*>)
is:
(<*>) :: (a -> b -> c) -> (a -> b) -> a -> c
(<*>) f g = \a -> f a (g a)
- Monad:
(>>=) :: (a -> b) -> (b -> a -> c) -> a -> c
(>>=) m k = Reader $ \r ->
runReader (k (runReader m r)) r
join :: (e -> e -> a) -> e -> a
join f x = f x x
runReader
:: Reader r a -- the Reader to run
-> r -- an initial environment
-> a -- extracted final value
Usage:
data Env = ...
createEnv :: IO Env
createEnv = ...
f :: Reader Env a
f = do
a <- g
pure a
g :: Reader Env a
g = do
env <- ask -- "Open the environment namespace into env"
a <- h env -- give env to h
pure a
h :: Env -> a
... -- use env and produce the result
main :: IO ()
main = do
env <- createEnv
a = runReader g env
...
In Haskell under normal circumstances impure functions should not directy call impure functions.
h
is an impure function, and createEnv
is impure function, so they should have intermediary.
Computations which accumulate monoid data to a shared Haskell storage. So * is parametrized by monoidal type.
Accumulator is maintained separately from the returned values.
Shared value modified through Writer monad methods.
* frees creator and code from manually keeping the track of accumulation.
Bind: The bound function is applied to the input value, bound function allowed to <>
to the accumulator.
type Writer r = WriterT r Identity
Example:
f :: Monoid b => a -> (a, b)
f a = if _condition_
then runWriter $ g a
else runWriter do
a1 <- h a
pure a1
g :: Monoid b => Writer b a
g a = do
tell _value1_ -- accumulator <> _value1_
pure a -- observe that accumulator stored inside monad
-- and only a main value needs to be returned.
h :: Monoid b => Writer b a
h a = do
tell _value2_ -- accumulator <> _value_
pure a
runWriter :: Writer w a -> (a, w) -- Unwrap a writer computation
-- as a (result, accumulator) pair.
-- The inverse of writer.
WriterT
, Writer
unnecessarily keeps the entire logs in the memory. Use fast-logger
for logging.
Computations that pass-over a state.
The bound function is applied to the input value to produce a state transition function which is applied to the input state.
Pure functional language cannot update values in place because it violates referential transparency.
type State s = StateT s Identity
Binding copies and transforms the state parameter through the sequence of the bound functions so that the same state storage is never used twice. Overall this gives the illusion of in-place update to the programmer and in the code, while in fact the autogenerated transition functions handle the state changes.
Example type: State st a
State
describes functions that consume a state and produce a tuple of result and an updated state.
Monad manages the state with the next process:
Where:
- f - processsor making function
- pA, pAB, pB - state processors
- sN - states
- vN - values
Bind with a processor making function from state procesor (pA) creates a new state processor (pAB). The wrapping and unwrapping by State/runState is implicit.
* is a practical solution to the current functional programming situation that generally monads do not have composition ability. In other words many monads can not be composed.
* is a special monad that extends other monad with extra funcitonality, it is a convinience mechanism, the functionality itself always can be developed in some other way. Sometimes transformers can make things way harder (especially profound for concurrency (Michael Snoyman - Monad Transformer State)) then other ways of implementation, especially when transformers hold some structure information (state-like information, in ExceptT, StateT)
Monad is not closed under compostion. Composition of monadic types does not always results in monadic type.
Basic case: during implementation of monadic composition, as a result type m T m a
arises, which does not allow join
transformation for the m
monadic layers or to have a regular unit transformation.
Monads that are * are the monads that have own properties as also ability to compose with any other monadand extend it with own properties. * use their implementation to solve the compostion type layering and allow to attach desirable property to result.
* solve monad composition and type layering by using own structure and information about itself. It is often that process involves a catamorphism of a * type layer.
Transformers have a light wrapper around the data that tags the modification with this transformer.
In type signatures of transformers *T m
- m
is already an extended monad, so *T
is just a wrapper to point that out.
Main monadic structure m
is wrapped around the internal data (core is a
). The structure that corresponds to the transformer creation properties (if it emitted by \( η \) of a transformer), goes into m
. Open parameters go external to the m
.
newtype ExceptT e m a =
ExceptT { runExceptT :: m (Either e a) }
newtype MaybeT m a =
MaybeT { runMaybeT :: m (Maybe a) }
newtype ReaderT r m a =
ReaderT { runReaderT :: r -> m a }
This has an effect that on stacking monad transformers, m
becomes monad stack, and every next transformer injects the transformer creation-specific properies \( η \) inside the stack, so out-most transformer has inner-most structure. Base monad is structurally the outermost.
* extends monads by injecting Maybe layer underneath monad, and processing that structure:
newtype MaybeT m a = MaybeT { runMaybeT :: m (Maybe a) }
* extends monads by injecting Either layer underneath monad, and processing that structure:
newtype EitherT e m a = EitherT { runEitherT :: m (Either e a) }
EitherT
of either
package gets replaced by ExceptT
of transformers
or mtl
packages.
Definition:
newtype ReaderT r m a = ReaderT { runReaderT :: r -> m a }
* functions: input monad m a
, out: m a
wrapped it in a free-variable r
(partially applied function).
That allows to use transformed m a
, now it requires and can use the r
passed environment.
To create a Reader monad:
type Reader r = ReaderT r Identity
Allows to lift monadic actions into a larger context in a neutral way.
pure
takes a parametric type and embodies it into constructed structure (talking of monad transformers - structure of the stacked monads).
lift
takes monad and extends it with a transformer.
In fact, for monad transformers - lift
is a last stage of the pure
, it follows from the lift property.
Method:
lift :: Monad m => m a -> t m a
Lift a computation from the argument monad to the constructed monad.
Neutral means:
lift . return = return
lift (m >>= f) = lift m >>= (lift . f)
The general pattern with MonadTrans instances is that it is usually lifts the injection of the known structure of transformer over some Monad.
lift embeds one monadic action into monad transformer.
The difference between pure, lift and MaybeT contructor becomes clearer if you look at the types:
Example, for MaybeT IO a
:
pure :: a -> MaybeT IO a
lift :: IO a -> MaybeT IO a
MaybeT :: IO (Maybe a) -> MaybeT IO a
x = (undefined :: IO a)
:t (pure x)
(pure x) :: Applicative t => t (IO a) -- t recieves one argument of product type
:t (pure x :: MaybeT IO a)
-- Expected type: MaybeT IO a1
-- Actual type: MaybeT IO (IO a0)
-- While the real type would be
:t (pure x :: MaybeT IO (IO a))
(pure x :: MaybeT IO (IO a)) :: MaybeT IO (IO a)
-- This goes into a conflict of what type&kind (* -> *) transformer constructor
-- awaits, and `m (m a)` is a layering we not interested in.
:t (lift x)
(lift x) :: MonadTrans t => t IO a -- result is a proper expected product type
-- To belabour
:t (lift x :: MaybeT IO a)
(lift x) :: MonadTrans t => t IO a -- result is a proper expected product type
lift
is a natural transformation \( η \) from an Identity monad (functor) with other monad as content into transformer monad (functor), with the preservation of the conteined monad:
-- Abstract monads with content as parameters. Define '~>' as a family of
-- morphisms that translate one functor into another (natural transformation)
type f ~> g = forall x. f x -> g x
-- follows
lift :: m ~> t m
* - allows to lift IO action until reaching the IO monad layer at the top of the Monad
stack (which is allways in the Haskell code that does IO).
class (Monad m) => MonadIO m where
liftIO :: IO a -> m a
liftIO
properties:
liftIO . pure = pure
liftIO (m >>= f) = liftIO m >>= (liftIO . f)
Which is identical properties to MonadTrans lift
.
Since lift
is one step, and liftIO all steps - all steps defined in terms of one step and all other steps, so the most frequent implementation is self-recursive lift . liftIO
:
liftIO ioa = lift $ liftIO ioa
<<<liftIO>>>
SCHT: <2020-06-30 Tue>
Monoid over applicative. Has left catch property.
Allows to run simultaneously several instances of a computation (or computations) and from them yeld one result by property from (<|>) :: Type -> Type -> Type
.
Minimal complete definition:
empty :: f a -- The identity element of <|>
(<|>) :: f a -> f a -> f a -- Associative binary operation
Additional functions some
and many
defined (automatically derived) as the least solutions to the equations:
some v = (:) <$> v <*> many v
many v = some v <|> pure []
-- => some v = (:) <$> v <*> $ some v <|> pure []
some :: f a -> f [a] -- One or more. Keep trying applying f to a until it succeeds at least once, and then keep doing it until it fails.
more :: f a -> f [a] -- Zero or more. Apply f to a as many times as you can until failure.
So there in the process should be found a definitive case of failure termination rule or otherwise process would never terminate.
To start understand intuitive difference:
> some Nothing
Nothing
> many Nothing
Just []
Perhaps it helps to see how some would be written with monadic do syntax:
some f = do
x <- f
xs <- many f
return (x:xs)
So some f
runs f
once, then ”many
” times, and conses the results. many f
runs f
”some
” times, or ”alternative
‘ly” just returns the empty list. The idea is that they both run f
as often as possible until it “fails”, and after that - compose the list of results. The difference is that some f
fails if f
fails immediately, while many f
will succeed and “return” the empty list. But what this all means exactly depends on how <|> is defined.
Is it only useful for parsing? Let’s see what it does for the instances in base: Maybe, [] and STM.
First Maybe. Nothing means failure, so some Nothing fails as well and evaluates to Nothing while many Nothing succeeds and evaluates to Just []. Both some (Just ()) and many (Just ()) never return, because Just () never fails! In a sense they evaluate to Just (repeat ()).
For lists, [] means failure, so some [] evaluates to [] (no answers) while many [] evaluates to [[]] (there’s one answer and it is the empty list). Again some [()] and many [()] don’t return. Expanding the instances, some [()] means fmap (():) (many [()]) and many [()] means some [()] ++ [[]], so you could say that many [()] is the same as tails (repeat ()).
For STM, failure means that the transaction has to be retried. So some retry will retry itself, while many retry will simply return the empty list. some f and many f will run f repeatedly until it retries. I’m not sure if this is useful thing, but I’m guessing it isn’t.
So, for Maybe, [] and STM many and some don’t seem to be that useful. It is only useful if the applicative has some kind of state that makes failure increasingly likely when running the same thing over and over. For parsers this is the input which is shrinking with every successful match.
<<<Alternative>>>
Functors between monoidal categories that preserves monoidal structure.
Get & set a value inside Functor.
<$
SCHT: <2020-06-21 Sun>
Functor that takes as an argument the product of types.
Or if combine it with product - accepts multiple argumets, so from that constructs “source” product category (Cartesian product) of categories, and realizes a functor from product category to target category.
Concept works over N type arguments instead of one.
Generalizes the concept of functor between categories, canonical morphisms between multicategories.
Any product or sum in a Cartesian category is a *.
In Haskell there is only one category, Hask, so in Haskell * is still endofunctor \( (Hask × Hask) → Hask ⇒ | (Hask × Hask) ≡ Hask | ⇒ Hask → Hask \).
Code definition:
class Bifunctor f
where
bimap :: (a -> a') -> (b -> b') -> f a b -> f a' b'
bimap f g = first f . second g
first :: (a -> a') -> f a b -> f a' b
first f = bimap f id
second :: (b -> b') -> f a b -> f a b'
second = bimap id
<<<Bifunctor>>>
Category of Haskell where objects are types and morphisms are functions.
It is a hypothetical category at the moment, since undefined and bottom values break the theory, is not Cartesian closed, it does not have sums, products, or initial object, ()
is not a terminal object, monad identities fail for almost all instances of the Monad class.
That is why Haskell developers think in subset of Haskell where types do not have bottom values. This only includes functions that terminate, and typically only finite values. The corresponding category has the expected initial and terminal objects, sums and products, and instances of Functor and Monad really are endofunctors and monads.
Hask contains subcategories, like Lst containing only list types.
Haskell and Category concepts:
- Things that take a type and return another type are type constructors.
- Things that take a function and return another function are higher-order functions.
<<<Hask>>>
SCHT: <2020-11-21 Sat>
\textgreek{μορφή} morphe form
Arrow between two objects inside a category.
Morphism can be anything.
Morphism is a generalization (\( f(x*y) ≡ f(x) \diamond f(y) \)) of homomorphism (\( f(x*y) ≡ f(x) * f(y) \)).
Since general morphisms not so much often ment and discussed - under morphism people almost always really mean the meaning of homomorphism-like properties, hense they discuss the algebraic structures (types) and homomorphisms between them.
In most usage, on a level under the objects: * is most often means a map (relation) that translates from one mathematical structure (that source object represents) to another (that target object represents) (that is called (somewhat, somehow) “structure-preserving”, but that phrase still means that translation can be lossy and irrevertable, so it is only bear reassemblence of preservation), and in the end the morphism can be anything and not hold to this conditions.
Morphism needs to correspond to function requirements to be it.
<<<Morphisms>>> <<<Arrow>>> <<<Arrows>>>
SCHT: <2020-05-12 Tue>
\textgreek{ὁμός} homos same (was chosen becouse of initial Anglish mistranslation to “similar”)
\textgreek{μορφή} morphe form
similar form
* map between two algebraic structures of the same type that preserves the operations.
\( f(x*y) ≡ f(x) * f(y) \), where for \( fA → B \) - \( A, B \) are sets with additonal algebraic structures (algebras) that include operation ∗; \( x,\ y \) are elements of the set \( B \).
* sends identity morphisms to identity morphisms and inverses to inverses.
The concept of * has been generalized under the name of morphism to many structures that either do not have an underlying set, or are not algebraic, or do not preserve the operation.
<<<Homomorphic>>>
Identity morphism - or simply identity: \( x ∈ C : \; idx=1x : x → x \) Composed with other morphism gives same morphism.
Corresponds to Reflexivity and Automorphism.
SCHT: <2020-08-08 Sat>
Identity only possible with morphism. See Identity morphism.
There is also distinct Zero value.
SCHT: <2020-09-18 Fri>
\( P(e,a)=P(a,e)=a \ | \ ∃ e ∈ S, ∀ a ∈ S \) \( P() \) is commutative.
Predicate
SCHT: <2020-10-24 Sat>
\( ∃ e ∈ S, ∀ a ∈ S : \; P(e,a)=a \)
Predicate
SCHT: <2020-10-10 Sat>
\( P(a,e)=a \; | \; ∃ e ∈ S, ∀ a ∈ S \)
Predicate
Return itself. (\ x.x)
id :: a -> a
\textgreek{μονο} mono only
\textgreek{μορφή} morphe form
Maps one to one (uniquely), so invertable (always has inverse morphism), so preserves the information/structure. Domain can be equal or less to the codomain.
\( fX → Y, \ ∀ x ∈ X \, ∃! y=f(x) \vDash f(x) ≡ fmono(x) \) - from homomorphism context \( fmono ˆ g1 = fmono ˆ g2 \ \vDash \ g1 ≡ g2 \) - from general morphism context Thus * is left canselable.
If * is a function - it is injective. Initial set of f is fully uniquely mapped onto the image of f.
<<<Monomorphic>>> <<<Monomorphisms>>>
SCHT: <2021-05-19 Wed>
\textgreek{επι} epi on, over
\textgreek{μορφή} morphe form
* is end-equating morphism. Since epimorphism covers target fully - ∀ morphisms composed to its end (target) are fully active in composition and so fully comparable between each other.
Term end-equating is more direct, easy and clear then classic right-canselable
. Since “right” is collision between direction of composition (right to left) (and sometimes composition gets writted left to right), way it is drawn (left to right), and written \( C → D \) (left to right).
\( fX → Y, ∀ y ∈ Y \, ∃ f(x) \vDash f(x) ≡ fepi(x) \) - from homomorphism context \( g_1 ˆ fepi = g_2 ˆ fepi ⇒ \; g_1 ≡ g_2 \) - from general morphism context
In Set category if * is a function - it is surjective (image of it fully uses codomain) Codomain is a called a projection of the domain.
* fully maps into the target.
<<<Epimorphic>>> <<<Epimorphisms>>>
\textgreek{ἴσος} isos equal
\textgreek{μορφή} morphe form
Not equal, but equal for current intents and purposes.
Morphism that has inverse.
Almost equal, but not quite: (Integer, Bool)
& (Bool, Integer)
- but can be transformed losslessly into one another.
Bijective homomorphism is also isomorphism.
\( f-1, b → a ˆ fa → b ≡ 1^a, \; fa → b ˆ f-1, b → a ≡ 1^b \)
2 reasons for non-isomorphism:
- function at least ones collapses a values of domain into one value in codomain
- image (of a function in codomain) does not fill-in codomain. Then isomorphism can exists for image but not whole codomain.
Categories are isomorphic if there \( R ˆ L = ID \)
<<<Isomorphic>>> <<<Isomorphisms>>>
SCHT: <2020-05-01 Fri>
Holds up to isomorphism. (upon the transformation can be used as the same)
SCHT: <2021-07-02 Fri>
\textgreek{ενδο} endo internal
\textgreek{μορφή} morphe form
Arrow from object to itself. Endomorphism forms a monoid (object exists and category requirements already in place).
SCHT: <2020-06-28 Sun>
\textgreek{αυτο} auto self
\textgreek{μορφή} form form
Isomorphic endomorphism.
Corresponds to identity, reflexivity, permutation.
<<<Automorphic>>> <<<Automorphisms>>>
<<<Endomorphic>>> <<<Endomorphisms>>>
SCHT: <2020-06-24 Wed>
\textgreek{κατά} kata downward
\textgreek{μορφή} morphe form
Unique arrow from an initial algebra structure into different algebra structure.
* in FP is a generalization folding, deconstruction of a data structure into more primitive data structure using a functor F-algebra structure.
* reduces the structure to a lower level structure. * creates a projection of a structure to a lower level structure.
<<<Catamorphic>>> <<<Catamorphisms>>>
Rule name | Haskell |
---|---|
cata-cancel | cata phi . InF = phi . fmap (cata phi) |
cata-refl | cata InF = id |
cata-fusion | f . phi = phi . fmap f => f . cata phi = cata phi |
cata-compose | eps :: f :~> g => cata phi . cata (In . eps) = cata (phi . eps) |
catamorphism \( ˆ \) anamorphism
Expanding and collapsing the structure.
3.2.7.8.2.1.1 *<<<Hylomorphic>>> <<<Hylomorphisms>>>
SCHT: <2020-07-31 Fri>
Generalizes unfold.
Dual concept to catamorphism.
Increases the structure.
Morphism from a coalgebra to the final coalgebra for that endofunctor.
Is a function that generates a sequence by repeated application of the function to its previous result.
<<<Anamorphic>>> <<<Anamorphisms>>>
SCHT: <2021-03-02 Tue>
Kernel of a homomorphism is a number that measures the degree homomorphism fails to meet injectivity (AKA be monomorphic). It is a number of domain elements that fail injectivity:
- elements not included into morphism
- elements that collapse into one element in codomain
thou Kernel \( [ x | x ← 0 || x ≥ 2 ] \).
Denotation: \( \operatorname{ker}T = \{ \mathbf{v} ∈ V:T(\mathbf{v}) = \mathbf{0}W \} \).
SCHT: <2020-11-20 Fri>
Morphism of elements from the kernel. Complementary morphism of elements that make main morphism not monomorphic.
SCHT: <2021-07-02 Fri>
Category in which objects are sets, morphisms are functions.
Denotation: \( Set \)
Roughly * is:
trans :: F a -> G a
, while a
is polymorphic variable.
Naturality condition: \( ∀ \ a \ ∃ \ (F \ a → G \ a) \), or , analogous to parametric polymorphism in functions. Since * in a category, stating \( ∀ (F \ a → G \ a) \) Naturality condition means that all morphisms that take part in homotopy of source functor to target functor must exist, and that is the same, diagrams that take part in transformation, should commute, and different paths brins same result: if \( α \) - natural transformation, \( αa \) natural transformation component - \( G \ f ˆ αa = αb ˆ F \ f \). Since * are just a type of parametric polymorphic function - they can compose.
* (\( \overrightarrow{η}\mathcal{D} \)) is transforming : \( \overrightarrow{η}\mathcal{D} ˆ F\mathcal{C → D} = G\mathcal{C → D} \). * abstraction creates higher-language of Category theory, allowing to talk about the composition and transformation of complex entities.
It is a process of transforming \( F\mathcal{C → D} \) into \( G\mathcal{C → D} \) using existing morphisms in target category \( \mathcal{D} \).
Since it uses morphisms - it is structure-preserving transformation of one functor into another. Iy mostly a lossy transformation. Only existing morphisms cab make it exist.
Existence of * between two functors can be seen as some relation.
Can be observed to be a “morphism of functors”, especially in functor category. * by \( \overrightarrow{η}\mathcal{D}y^{\mathcal{C}}(\overrightarrow{(x,y)}\mathcal{C}) ˆ F\mathcal{C → D}(\overrightarrow{(x,y)}\mathcal{C}) = G\mathcal{C → D}(\overrightarrow{(x,y)}\mathcal{C}) ˆ \overrightarrow{η}\mathcal{D}x^{\mathcal{C}}(\overrightarrow{(x,y)}\mathcal{C}) \), often written short \( \overrightarrow{η}b ˆ F(\overrightarrow{f}) = G(\overrightarrow{f}) ˆ \overrightarrow{η}a \). Notice that the \( \overrightarrow{η}\mathcal{D}x^{\mathcal{C}}(\overrightarrow{(x,y)}\mathcal{C}) \) depends on objects&morphisms of \( \mathcal{C} \).
In words: * depends on \( F \) and \( G \) functors, ability of \( D \) morphisms to do a homotopy of \( F \) to \( G \), and *:
- for every object in \( \mathcal{C} \) picks natural transformation component in \( \mathcal{D} \).
- for every morphism in \( \mathcal{C} \) picks the commuting diagram in \( \mathcal{D} \), called <<<naturality square>>>.
Also see: Natural transformation in Haskell
Knowledge of * forms a 2-category.
Can be composed
- “vertically”:
\begin{tikzcd}
a \arrow[rrrr, “F”, bend left] \arrow[rrrr, “G”, bend right] \arrow[rrrr, “H”, bend right=60] & & ⇓{α} & & b
& & ⇓{β}
\end{tikzcd}
\begin{tikzcd} a \arrow[rrrr, “F”, bend left] \arrow[rrrr, “H”, bend right=49] & & ⇓{β\circα} & & b \end{tikzcd}
- “horizontally” (“Godement product”):
\begin{tikzcd} a \arrow[rr, “F1”, bend left] \arrow[rr, “G1”, bend right] & ⇓{α} & b \arrow[rr, “F2”, bend left] \arrow[rr, “G2”, bend right] & ⇓{β} & c \end{tikzcd}
\begin{tikzcd} a \arrow[rr, “F2 ˆ F1”, bend left] \arrow[rr, “G2 ˆ G1”, bend right] & ⇓{β * α} & c \end{tikzcd}
Vertical and horizontal compositions can be done in any order, they abide the exchange property.
<<<Natural transformations>>> <<<Naturality condition>>> <<<Naturality>>>
\( \overrightarrow{η}\mathcal{D}(x) = F\mathcal{D}(x) → G\mathcal{D}(x) \ | \ x ∈ \mathcal{C} \)
<<<Component of natural transformation>>>
SCHT: <2020-06-23 Tue>
Family of parametric polymorphism functions between endofunctors.
In Hask is \( F \ a → G \ a \). Can be analogued to repackaging data into another container, never modifies the object content, it only if - can delete it, because operation is lossy.
Can be sees as ortogonal to functors.
Category where:
Part | Is | # | |
---|---|---|---|
* | object | category | 0-cell |
⇒ | morphism | functor | 1-cell |
⇒ | 2-morphism | natural transformation, morphisms homotopy | 2-cell |
\begin{tikzcd} a \arrow[rrrr, “F”, bend left] \arrow[rrrr, “G”, bend right] & & ⇓{nt} & & b \end{tikzcd}
Is Cartesian closed category.
<<<Cat>>> <<<2-category>>>
2-category that is enriched and lax.
For handling relaxed associativity - introduces associator, and for identity l -eft/right unitor.
Forming from bicategories higher categories by stacking levels of abstraction of such categories - leads to explosion of special cases, differences of every level, and so overall difficulties.
Stacking groupoids (category in which are morphisms are invertable) is much more homogenous up to infinity, and forms base of the homotopy type theory.
SCHT: <2021-03-05 Fri>
Category duality behaves like a logical inverse.
Inverse \( \mathcal{C} \) = \( \mathcal{C}op \) - inverts the direction of morphisms.
Composition accordingly changes to the morphisms: \( (g ˆ f)op = fop ˆ gop \)
Any statement in the terms of \( \mathcal{C} \) in \( \mathcal{C}op \) has the dual - the logical inverse that is true in \( \mathcal {C}op \) terms.
Opposite preserves properties:
- products: \( (\mathcal{C} × \mathcal{D})op ≅ \mathcal{C}op × \mathcal{D}op \)
- functors: \( (F\mathcal{C → \mathcal{D}})op ≅ F\mathcal{Cop → \mathcal{D}op} \)
- slices: \( (\mathcal{F} ↓ \mathcal{G})op ≅ (\mathcal{G}op ↓ \mathcal{F}op) \)
<<<Opposite category>>> <<<Opposite categories>>> <<<Category duality>>> <<<Duality>>> <<<Dual category>>> <<<Dual>>>
Structures that are dual (in the category-theoretic sense of reversing arrows) to unital associative algebras. Every coalgebra, by vector space duality, reversing arrows - gives rise to an algebra. In finite dimensions, this duality goes in both directions. In infinite - it should be determined.
∀ Hom sets contain zero or one morphism.
\( f ≡ g \ | \ ∀ x,y \ ∀ f,g: x → y \)
A proset (preordered set).
<<<Proset category>>> <<<Prosetal category>>> <<<Poset category>>> <<<Posetal category>>>
Establishes equality in morphisms that have same source and target.
Draws the morphisms that are: \( f = g ⇒ \{f, y\}: X → Y \)
<<<Diagram commutes>>> <<<Commutes>>>
Algorythm of constructing definitions in Category theory. Specially good to translate properties/definitions from other theories (Set theory) to Categories.
Method:
- Define a pattern that you defining.
- Establish ranking for pattern matches.
- The top of ranking, the best match or set of matches - is the thing you was looking for. Matches are isomorphic for defined rules.
* uses Yoneda lemma, and as such constructions are defined until isomorphism, and so isomorphic betweem each-other.
<<<Universal constructions>>>
Universal construction:
\begin{matrix}
&& c′ &&
& {}^p\swarrow\phantom{{}p} & {\tiny \phantom{!}}↓{\tiny !} & \phantom{{}^q}\searrow^q& \
a & \underset{π_a}{←} & c & \underset{π_b}{→} & b
\end{matrix}
Pattern: \( p: c → a, \ q: c → b \)
Ranking: \( max{∑∀{(!: c′ → c \ | \ p′ = p ˆ !, \ q′ = q ˆ !)}} \)
\( c′ \) is another candidate.
For sets - Cartesian product.
* is a pair. Corresponds to product data type in Hask (inhabited with all elements of the Cartesian product).
Dual is Coproduct.
<<<Products>>>
Universal construction:
\begin{matrix}
&& c′ &&
& {}^p\nearrow\phantom{{}p} & {\tiny \phantom{!}}↑{\tiny !} & \phantom{{}^q}\nwarrow^q& \
a & \underset{ι_a}{→} & c & \underset{ι_b}{←} & b
\end{matrix}
Pattern: \( i: a → c, \ j: b → c \)
Ranking: \( max{∑∀{(!: c → c′ \ | \ i′ = ! ˆ i, \ j′ = ! ˆ j)}} \)
\( c′ \) is another candidate.
For sets - Disjoint union.
* is a set assembled from other two sets, in Haskell it is a tagged set (analogous to disjoint union).
Dual is Product.
<<<Coproducts>>>
SCHT: <2020-05-01 Fri>
General particular structure. In which structure, properties autofollows from definition, axioms.
Also uses as a term when surcomstances of structures, rules, properties, axioms used coinside with the definition of a particular object \therefore form object of this type with the according properties and possibilities.
Category which is includded into a bigger category.
SCHT: <2020-07-02 Thu>
All morphisms from source object to target object.
Denotation: \( homC(X,Y) = (∀ f: X → Y) = hom(X,Y) = C(X,Y) \) Denotation was not standartized.
Hom sets belong to Set category.
In Set category: \( ∃! (a, b) \iff ∃! Hom \), \( ∀ Hom ∈ \ Set \). Set category is special, Hom sets are also objects of it.
Category can include Set, and hom sets, or not.
<<<Hom-set>>> <<<Hom sets>>>
SCHT: <2020-05-07 Thu>
\( hom:\mathcal{C}op × \mathcal{C} → Set \) Functor from the product of \( \mathcal{C} \) with its opposite category to the category of sets.
Denotation variants: \( H_A = \mathrm{Hom}(-, A) \) \( h_A = {\cal \mathcal{C}}(-, A) \) \( Hom(A,-): \ \mathcal{C} → Set \)
Hom-bifunctor: \( Hom(-,-): \ \mathcal{C}op × \mathcal{C} → Set \)
Generalises the notion of function set to internal object. As also hom set to internal hom objects.
Cartesian closed (monoidal) category strictly required, as * multiplicaton holds composition requirement:
\( ˆ:hom(y,z) ⊗ hom(x,y) → hom(x,z) \)
Denotation: \( ba \)
Universal construction:
\begin{tikzcd}
c \arrow[dd, “u”, dotted] & & c × a \arrow[dd, “u × 1a”, dotted] \arrow[rrdd, “g”] \arrow[ll] & &
& & & & \
ba & & ba × a \arrow[rr, “eval”, dotted] \arrow[ll] & & b
\end{tikzcd}
, where in Category: \( ba \) - exponential object, × - product bifunctor, \( a \) - argument of *, \( b \) - result, \( c \) - candidate, \( ba ≡ ( a ⇒ b ) \) - *.
* \( ba \) (also as \( (a ⇒ b) \)) represent exponentiation of cardinality of \( ∀ ba \) possiblities.
<<<Function object>>> <<<Internal hom>>> <<<Exponential objects>>> <<<Hom object>>> <<<Hom objects>>>
Uses Hom objects (exponential objects), which do not belong into Set category. Category is no longer small, now may be called large.
\( hom(x,y) ∈ K \).
Called: * over K
(whick holds hom objects).
<<<Enriched>>> <<<Large category>>>
The category of magmas, denoted \( Mag \), has as objects - sets with a binary operation, and morphisms given by homomorphisms of operations (in the universal algebra sense).
<<<MAG>>> <<<Magma category>>> <<<Category of magmas>>>
SCHT: <2020-07-22 Wed>
Set of values. For type to have sence the values must share some sence, properties.
<<<Type>>> <<<Types>>> <<<Data types>>>
SCHT: <2021-03-12 Fri>
Data type recieved by ->inferring->compiling->execution.
Composite type formed by combining other types.
<<<AlgDT>>>
SCHT: <2020-05-26 Tue>
Number of possible implementations for a given type signature.
Disjunction, sum - adds cardinalities. Conjunction, product - multiplies cardinalities.
<<<Cardinalities>>>
* - constant value; nullary data constructor.
One instance that inhabit data type.
Data type declaration is the most general and versatile form to create a new data type. Form:
data [context =>] type typeVars1..n
= con1 c1t1..i
| ...
| conm cmt1..q
[deriving]
SCHT: <2020-07-21 Tue>
When type and values have relation between them. Type has restrictions for values, value of a type variable has a result on the type.
<<<Dependent types>>>
SCHT: <2020-06-27 Sat>
Generator. Gen type is to generate pseudo-random values for parent type. Produces a list of values that gets infinitely cycled.
SCHT: <2020-06-03 Wed>
Any combination of * and ->
Type that take more types as arguments.
Humbly really a function
<<<Higher-kinded data types>>>
SCHT: <2021-04-18 Sun>
Create a new type from old type by attaching a new constructor, allowing type class instance declaration.
newtype FirstName = FirstName String
Data will have exactly the same representation at runtime, as the type that is wrapped.
newtype Book = Book (Int, Int)
(,)
/ \
Integer Integer
SCHT: <2020-06-20 Sat>
The most generic data type that still typechecks.
SCHT: <2021-04-26 Mon>
Is an algebraic data type respesentation of a product construction.
Formed by logical conjunction (AND
, ’* *
’).
Haskell forms:
-- 1. As a tuple (the uncurried & most true-form)
(T1, T2)
-- 2. Curried form, data constructor that takes two types
C T1 T2
-- 3. Using record syntax. =r# <inhabitant>= would return the respective =T#=.
C { r1 :: T1
, r2 :: T2
}
<<<Product type>>>
SCHT: <2020-08-18 Tue>
Enumerated (ordered) set. Set with a strict order property.
Denotation:
()
( , )
( , , )
( , , ... )
More general mathematical denotation was not established, variants: \( (n)n ∈ \mathbb{N} \) \( ω → X \) \( \{ i:Ord \ | \ i < α \} \)
In Haskell: Data type that stores multiple ordered values withing a single value.
Name | Arity | Denotation |
---|---|---|
Unit, empty | 0 | () |
Singleton | 1 | (_) |
<<<Tuple>>>, pair, <<<two-tuple>>> | 2 | ( , ) |
<<<Triple>>>, three-tuple | 3 | ( , , ) |
Sequence | N | ( , , ...) |
<<<Sequences>>> <<<Tuples>>> <<<Ordered pair>>> <<<Ordered triple>>>
SCHT: <2020-08-15 Sat>
Sequence of one type objects.
Denotation:
[]
[ , ]
[ , , ]
[ , , ... ]
Haskell definition:
data [] a = [] | a : [a]
Definition is self-referrential (self-recursive), can be seen as anamorphism (unfold) of the []
(empty list, memory cell which is container of particular type) and :
(cons operation, pointer). As such - can create non-terminating data type (and computation), in other words - infinite.
Proxy type holds no data, but has a phantom parameter of arbitrary type (or even kind). Able to provide type information, even though has no value of that type (or it can be may too costly to create one).
data Proxy a = ProxyValue
let proxy1 = (ProxyValue :: Proxy Int) -- a has kind `Type`
let proxy2 = (ProxyValue :: Proxy List) -- a has kind `Type -> Type`
SCHT: <2020-12-15 Tue>
Type check takes place at compile level, so compiled program already has expectations of types it should recieve.
Mathematical type. They form into structural type system.
<<<Structural>>>
SCHT: <2020-06-22 Mon>
Strict global hierarchy and relationships of types and their properties. Haskell type system is *. In most languages typing is name-based, not structural.
<<<Structural typing>>>
SCHT: <2020-07-25 Sat>
Algebraic data type formed by logical disjunction (OR ‘|’).
SCHT: <2021-01-02 Sat>
Create new type constructor, and use all data structure of the base type.
SCHT: <2020-07-19 Sun>
Type system construct that adds a support of ad hoc polymorphism.
Type class makes a nice way for defining behaviour, properties over many types/objects at once.
Type classes with multiple parameters are relations on types.
<<<Type classes>>>
SCHT: <2020-10-11 Sun>
Type class of QuickCheck.Arbitrary (that is reexported by QuickCheck) for creating a generator/distribution of values. Useful function is arbitrary - that autogenerates values.
Depends on type and generates values of that type.
SCHT: <2020-07-21 Tue>
Pseudogenerates a function basing on resulting type.
coarbitrary :: CoArbitrary a => a -> Gen b -> Gen b
<<<CoArbitrary>>>
Allows dynamic type checking in Haskell for a type. Shift a typechecking of type from compile time to runtime. * type gets wrapped in the universal type, that shifts the type checks to runtime.
Also allows:
- Get the type of something at runtime (ex. print the type of something
typeOf
). - Compare the types.
- Reifying functions from polymorphic type to conrete (for functions like
:: Typeable a => a -> String
).
<<<Typeable>>>
Type class has a superclass.
SCHT: <2020-07-22 Wed>
Type class instances sometimes can be automatically derived from the parent types.
Type classes such as Eq, Enum, Ord, Show can have instances generated based on definition of data type.
P.S.
Language options:
- DeriveAnyClass
- DeriveDataTypeable
- DeriveFoldable
- DeriveFunctor
- DeriveGeneric
- DeriveLift
- DeriveTraversable
- DerivingStrategies
- DerivingVia
- GeneralisedNewtypeDeriving
- StandaloneDeriving
<<<Derived>>> <<<Deriving>>>
* declares a promise of a relation that from one type would uniquly determine/determines another.
\(X → Y\) - “X determines Y”.
class C a b | a -> b
where
...
* are used for multi-parameter type classes. As some multi-parameter type classes with their methods create undecidable situations when method signature & use can not infer all parameters for instance of the type class. Solution in the case when one of the parameters can be determined from the others - * get declared, so (subordinate parameter) then for example can be the return type but none of the argument types of some of the methods, which allows type system to work propely.
SCHT: <2021-01-31 Sun>
Block of implementations of functions, based on unique type class->type pairing.
SCHT: <2020-06-23 Tue>
Nullary type constructor.
Name of the data type.
Constructor that takes type as an argument and produces new type.
SCHT: <2020-09-12 Sat>
Synonim for existing type. Uses the same data constructor.
type FirstName = String
Used to distinct one entities from other entities, while they have the same type. Also main type functions can operate on a new type.
SCHT: <2020-08-07 Fri>
* - is a _
or _name
in the expression. On evaluation GHC would show the derived type information which should be in place of the *. That information helps to fill in the gap.
<<<Typed holes>>>
SCHT: <2020-12-24 Thu>
Automatic data type detection for expression.
<<<Inferring>>> <<<Infer>>> <<<Infers>>> <<<Inferred>>>
Weak ordering of types.
The rank of polymorphic type shows at what level of nesting forall
quantifier appears.
Count-in only quantifiers that appear to the left of arrows.
f1 :: forall a b. a -> b -> a
-- =
f1 :: a -> b -> c
g1 :: forall a b. (Ord a, Eq b) => a -> b -> a
-- =
g1 :: (Ord a, Eq b) => a -> b -> a
f1, g1 - rank-1 types. Haskell itself implicitly adds universal quantification.
f2 :: (forall a. a->a) -> Int -> Int
g2 :: (forall a. Eq a => [a] -> a -> Bool) -> Int -> Int
f2, g2 - rank-2 types. Quantificator is on the left side of a →. Quantificator shows that type on the left can be overloaded.
Type inference in Rank-2 is possible, but not higher.
f3 :: ((forall a. a->a) -> Int) -> Bool -> Bool
f3 - rannk3-type. Has rank-2 types on the left of a →.
f :: Int -> (forall a. a -> a)
g :: Int -> Ord a => a -> a
f, g are rank 1. Quantifier appears to the right of an arrow, not to the left. These types are not Haskell 98. They are supported in RankNTypes.
<<<Type ranks>>> <<<Rank type>>> <<<Rank types>>> <<<Rank-1 type>>> <<<Rank-1 types>>> <<<Rank-2 type>>> <<<Rank-2 types>>> <<<Rank-3 type>>> <<<Rank-3 types>>>
SCHT: <2020-05-01 Fri>
Refers to an unspecified parametric polymorphic type (maybe with ad-hoc polymorphism constraints) (keeps a naturality condition) in Haskell type signature.
In Haskell are always introduced with keyword forall
explicit or implicit.
SCHT: <2020-07-27 Mon>
Type that directly exist on the hardware. The type abstraction can be completely removed. With unlifted types Haskel type system directly manages data in the hardware.
<<<Unlifted types>>>
SCHT: <2020-09-18 Fri>
Type system and algebra that also track the multiplicity of data. There are 3 general linear type groups:
- 0 - exists only at type level and is not allowed to be used at value level. Aka
s
in ST-Trick. - 1 - data that is not duplicated
- 1< - all other data, that can be duplicated multiple times.
<<<Linear types>>>
Data.List.NonEmpty Has a Semigroup instance but can’t have a Monoid instance. It never can be an empty list.
data NonEmpty a = a :| [a]
deriving (Eq, Ord, Show)
:| - an infix data costructor that takes two (type) arguments. In other words :| returns a product type of left and right
SCHT: <2020-06-20 Sat>
* - allows to check that behaviour conforms to the protocol.
So far very complex, not very productive (or well-established) topic.
SCHT: <2020-12-14 Mon>
Tree where every element is a Leaf (structure stub, Nothing) or a Node (split of branches):
data BinaryTree a
= Leaf
| Node (BinaryTree a) a (BinaryTree a)
SCHT: <2021-07-21 Wed>
A _
non-value in the type or pattern match expression, placeholder, fits for enything.
Denoted
_
<<<Bottom>>> <<<Bottom values>>>
SCHT: <2021-07-17 Sat>
Haskell * type class means to have lowest value & highest value, so a bounded range of values.
<<<Bounded>>>
SCHT: <2020-10-08 Thu>
- Type constructor
- Data constructor
Also see: Constant
<<<Constructors>>>
SCHT: <2020-08-07 Fri>
Type constraints for polymorphic variables. Written before the main type signature, denoted:
TypeClass a => ...
<<<Contexts>>>
SCHT: <2020-07-21 Tue>
Values that is a component of data type set.
data Maybe
= Nothing
| Just a
Does not represent the information why Nothing
happened.
For error - use Either.
Do not propagate *.
Handle * locally to where it is produced. Nothing
does not hold useful info for debugging & short-circuits the processes. Do not expect code type being bug-free, do not return Maybe
to end user since it would be impossible to debug, return something that preserves error information.
<<<Nodes>>>
SCHT: <2020-08-11 Tue>
Data type inferred from the text of the code.
SCHT: <2020-07-21 Tue>
- Abstract data type
- Algebraic data type
SCHT: <2020-07-22 Wed>
Fully resolved, definitive, non-polymorphic type.
When type constructor and data constructor have the same name.
Theoretically if person knows the rules - * can be solved, because in Haskell type and data declaration have different places of use.
Kind -> Type -> Data
<<<Kinds>>>
SCHT: <2020-05-20 Wed>
There is only one way to “perform” an I/O action: bind it to Main.main
of the program.
For function I/O it should be in IO monad and evaluated from Main.main
.
Type for values whose evaluations has a posibility to cause side effects or return unpredictable result. Haskell standard uses monad for constructing and transforming IO actions. IO action can be evaluated multiple times.
IO data type has unpure imperative actions inside. Haskell is pure Lambda calculus, and unpure IO integrates in the Haskell purely (type system abstracts IO unpurity inside IO data type).
IO sequences effect computation one after another in order of needed computation, or occurence:
twoBinds :: IO ()
twoBinds =
putStrLn "First:" >>
getLine >>=
\a ->
putStrLn "Second:" >>
getLine >>=
\b ->
putStrLn ("\nFirst: "
++ a ++ ".\nSecond "
++ b ++ ".")
main = twoBinds
Sequencing is achieved by compilation of effects performing only while they recieve the sugared-in & passed around the RealWorld
fake type value, that value in the every computation gets the new “value” and then passed to the next requestes computation. But special thing is about this parameter, this RealWorld
type value passed, but never looked at. GHC realizes, since value is never used, - it means value and type can be equated to ()
and moreover reduced from the code, and sequencing stays.
Finite combination of symbols that is well-formed according to context-free grammar.
Generally meaningless. Meaning gets derived from an * & context (and/or content words) by congruency with knowledge & expirience.
<<<Expressions>>>
SCHT: <2020-12-07 Mon>
* - mathematical expression that can be evaluated in a finite number of operations.
May contain:
- constants
- variables
- operations (e.g., + − × ÷)
- functions (e.g., nth root, exponent, logarithm, trigonometric functions, and inverse hyperbolic functions), but usually no limit.
Right-hand side of the expression.
Left-hand side of the expression.
SCHT: <2020-07-11 Sat>
Reducible expression.
SCHT: <2020-10-26 Mon>
Link together sequences, expressions.
SCHT: <2020-09-18 Fri>
Equivalence of a processes in expressions. If expressions have according parameters different, but the internal processes are literally the same process.
SCHT: <2020-05-01 Fri>
Expression that does not contain any free variables.
<<<Ground formula>>>
A name for expression.
\additional
There fequently can be heard: one of most notable Haskell properties is Haskell has immutable "variables"= (and term here used in the sence that imperative programmers frequently use). Logically we see statement is contradictory with itself: "variables" - something that has change as a defining propery - are not changing; it is a nonsencical statement. Please, read the saying as: =Haskell has immutable values
, due to following the value semantics: see “Value”. And Haskell expressions are functions (that are referentially transparent - meaning itself immutable) - and they are also values (hense term “functional programming” means - functions are first-class values). Since values bind to variables - people are wrongly mix-up terms and say their names (according ”*”) are immutable.
As you see in the code - Haskell variables (same names) hold different values at different times. Variables are reused, meaning “names are reused” - binded to different values on scope changes. But all values that Haskell holds - are, by the design of the language, are treated immutable, any transformations Haskell resolves by creating new values, and frees the space by freeing-up from no longer needed values.
<<<Variables>>>
SCHT: <2020-11-29 Sun>
Composable expression.
SCHT: <2020-06-27 Sat>
Full dependency of one quantity from another quantity.
Denotation: \( y = f(x) \) \( f: X → Y \), where \( X \) is domain, \( Y \) is codomain.
Directionality and property of invariability emerge from one another.
-- domain func codomain
* -> *
\( y(x) = (zx2 + bx + 3 \ | \ b = 5) \) ^ ^ ^^ ^ ^
| \( \textsubscript{Parameter} \) \( \textsubscript{Name of the function} \)\( \textsubscript{Var} \)\( \textsubscript{Constant} \) | |||
\( \textsubscript{Bound variable} \) | |||
\( \textsubscript{Free variable} \) | |||
Lambda abstraction is a function. Function is a mathematical operation.
Function = Total function = Pure function. Function theoretically can be to memoized.
Also see: Partial function Inverse function - often partially exists (partial function).
<<<Functions>>> <<<Bound variable>>>
SCHT: <2020-08-07 Fri>
Number of parameters of the function.
- nullary - f()
- unary - f(x)
- binary - f(x,y)
- ternary - f(x,y,z)
- n-ary - f(x,y,z..)
SCHT: <2020-07-06 Mon>
Function is a complete one-to-one pairing of elements of domain and codomain (image). It means function both surjective (so image == codomain) and injective (every domain element has unique correspondence to the image element).
For bijection inverse always exists.
Bijective operation holds the equivalence of domain and codomain.
Denotation:
⤖
>->>
f : X ⤖ Y
LaTeX needed to combine symbols: \( \newcommand*{\twoheadrghtarrowtail}{\mathrel{\rightarrowtail\kern-1.9ex\twoheadrightarrow}} f : X \twoheadrghtarrowtail Y \)
Corersponds to isomorphism.
<<<Bijective>>> <<<Bijective function>>>
SCHT: <2020-05-01 Fri>
Function without free variables. Higher-order function that uses only function application and other combinators.
\a -> a
\ a b -> a b
\f g x -> f (g x)
\f g x y -> f (g x y)
Not combinators:
\ xs -> sum xs
Informal broad meaning: referring to the style of organizing libraries centered around the idea of combining things.
SCHT: <2020-07-27 Mon>
Transforms two of the same type, applying same mediate transformation, and then transforming those into the result.
import Data.Function (on)
on :: (b -> b -> c) -> (a -> b) -> a -> a -> c
a--\b
* ---c
a--/b
<<<Psi-combinator>>> <<<On-combinator>>>
SCHT: <2020-06-22 Mon>
* - bind the argument to the parameter of a function, and do a beta-reduction.
<<<Apply>>> <<<Applied>>> <<<Applying>>> <<<Application>>>
Expression that haracterizes the process.
(.) :: (b -> c) -> (a -> b) -> a -> c
a -> (a -> b) -> (b -> c) -> c
In Haskell inline composition requires:
h.g.f $ i
<<<Composition>>> <<<Compose>>> <<<Composed>>>
SCHT: <2020-08-02 Sun>
Is a part with name of the function and it’s paramenters. AKA: \( f(x) \)
SCHT: <2020-05-01 Fri>
The range of a function refers to either the codomain or the image of the function, depending upon usage. Modern usage almost always uses range to mean image. So, see Function image.
SCHT: <2020-09-17 Thu>
Function that has arity > 1.
\additional
HOF is:
- function that accepts function as a parameter
- function that has more then one parameter.
Application of an argument to * produces a function that has arity - 1
.
<<<HOF>>>
SCHT: <2020-05-18 Mon>
Catamorphism of a structure to a lower type of structure. Often to a single value.
* is a higher-order function that takes a function which operates with both main structure and accumulator structure, * applies units of data structure to a function wich works with accumulator. Upoun traversing the whole structure - the accumulator is returned.
Function one-to-one injects from domain into codomain.
Keeps distinct pairing of elements of domain and image. Every element in image coresponds to one element in domain.
\( ∀ a,b ∈ X, \; f(a)=f(b) ⇒ a=b \)
\( ∃ (inverse \ function) \ | \ ∀ (injective \ function) \)
Denotion:
↣
>->
f : X ↣ Y
Corresponds to Monomorphism.
<<<Injective>>> <<<Injective function>>> <<<Injectivity>>>
SCHT: <2020-05-03 Sun>
One that does not cover all domain. Unsafe and causes trouble.
SCHT: <2020-08-01 Sat>
* means properly abstracted.
If the contrary - abstraction is unpure.
Also see: pure function.
<<<Pure>>>
Function that is pure \( ≡ \) referentially transparent function.
SCHT: <2020-05-31 Sun>
Writing function in a parentheses. Allows to pass around partially applied functions.
SCHT: <2021-01-21 Thu>
Function uses codomain fully.
\( ∀ y ∈ Y, ∃ x ∈ X \)
Denotation: \( f : X \twoheadrightarrow Y \)
Corresponds to Epimorphism.
<<<Surjective>>> <<<Surjective function>>>
SCHT: <2021-02-16 Tue>
Function that does not cover at least one edge case.
<<<Unsafe>>>
SCHT: <2020-07-21 Tue>
* - having variable arity (often up to indefinite).
SCHT: <2020-05-01 Fri>
Source set of a function. \( X \) in \( X → Y \).
SCHT: <2020-07-07 Tue>
\( Y \) in
SCHT: <2020-06-11 Thu>
Logical function that has arity and produces proposition.
SCHT: <2020-09-14 Mon>
Repeated function application when sometimes the same function gets called.
Allows computations that may require indefinite amount of work.
<<<Recursive>>>
SCHT: <2020-06-21 Sun>
A part of a recursive function that trivially produces result.
Tail calls are recursive invocantions of itself.
Type of the parameter changes in recursive invocations of function.
Is always a higher-ranked type.
<<<Milner–Mycroft typability>>> <<<Milner–Mycroft calculus>>>
SCHT: <2020-07-28 Tue>
Variable in the fuction that is not bound by the head. Until there are * - function stays partially applied.
SCHT: <2020-05-23 Sat>
It is a property of \(\{f\mathcal{X → X}, \mathcal{X}\}\) (function & a set it operates on).
\( f(x) = f\mathcal{X → X} \ | \ ∀ x ∈ \mathcal{X} \), \( \mathcal{X} \) is closed under \( f \), it is a trivial case when operation is legitimate for all values of the domain.
Operation on members of the domain always produces a members of the domain. The domain is closed under the operation.
It is a powerful property. For example:
- it allows to apply algebra operations (\(\{*,/,+,-\}\)) without “does operation fits” to any numbers in the numbers in the \(\mathbb{R}\), because those operations are closed under the \(\mathbb{R}\), with a caveat of small caveat of \(0\) for \(/\).
- it allows to apply and compose endofunctors on categories without thought or remorse of whenever that would work, since any combination of them works. Because
fmap
defined for all[]
or forMaybe
and does not changes structure. For example one can applyfmap
to[Maybe a]
to a list, or composefmap
of `Maybe` withfmap
of[]
(in Haskell just compoe twicefmap . fmap
) to work on theMaybe a
values inside[]
. Again, because Haskell functors are endofunctors defined on the whole type which is polymorphic inside, so the definitions of Haskell endofunctors are closed in types they apply to.
In the case when there is a domain values for which operation is not legitimate/not exists:
\( f(x) = f\mathcal{V → X} \ | \ \mathcal{V ∈ X}, ∀ x ∈ \mathcal{V} \), \( \mathcal{X} \) is closed under \( f \).
<<<Closed>>>
SCHT: <2020-06-28 Sun>
παρά para subsidiary μέτρον metron measure
Named varible of a function.
Argument is a supplied value to a function parameter.
Parameter (formal parameter) is an irrefutable pattern, and implemeted that way in Haskell.
<<<Parameters>>> <<<Formal parameter>>> <<<Formal parameters>>>
Part of function parameters applied.
<<<Partially applied>>>
SCHT: <2020-05-01 Fri>
Expression, logical function that is/can produce a proposition.
Well formed formula WFF wff WFFS wffs
ὁμός homós same
One can be “continuously deformed” into the other.
For example - functions, functors. Natural transformation is a homotopy of functors.
<<<Homotopies>>> <<<Homotopic>>>
SCHT: <2020-05-01 Fri>
Universal model of computation. Which means * can implement any Turing machine. Based on function abstraction and application by substituting variables and binding values.
* has lambda terms:
- variable (\( x \))
- application (\( (ts) \))
- abstraction (lambda function) (\( (λ x . t) \))
<<<Lambda term>>> <<<Lambda terms>>>
SCHT: <2020-06-12 Fri>
λ-cube shows the 3 dimentions of generalizations from simply typed Lambda calculus to Calculus of constructions.
\additional
\begin{tikzcd}
{Polymorphic \ types}
& {Type \ opertations} \
0 \arrow[uu] \arrow[ur] \arrow[rr] & & {Dependent \ types}
\end{tikzcd}
\begin{tikzcd}[row sep=scriptsize,column sep=scriptsize]
& λ ω \arrow[rr] \arrow[from=dd] & & λ C
λ 2 \arrow[ur] \arrow[rr, crossing over] & & λ P 2 \arrow[ur] \
& λ \underline{ω} \arrow[rr] & & λ P \underline{ω} \arrow[uu] \
λ \arrow[rr] \arrow[uu] \arrow[ur] & & λ P \arrow[uu, crossing over] \arrow[ur]
\end{tikzcd}
Each dimension of the cube corresponds to extensions (a new type of relation of objects depending on objects):
Denotation | Name | Programming | New type of relations |
---|---|---|---|
2 | Polymorphic types | First-class polymorphism of types | Terms depending on types |
ω | Type operation | Type class, type families | Types depending on types |
P | Dependent types | Higher-rank polymorphism, dependent types | Types depending on terms |
Denotation | Logical system |
---|---|
\( λ\to \) | (First Order) Propositional Calculus |
\( λ2 \) | Second Order Propositional Caculus |
\( λ\omega \) | Weakly Higher Order Propositional Calculus |
\( λ \underline{ω} \) | Higher Order Propositional Calculus |
\( λ P \) | (First Order) Predicate Logic |
\( λ P 2 \) | Second Order Predicate Calculus |
\( λ P \undeline{ω} \) | Weak Higher Order Predicate Calculus |
\( λ C \) | Calculus of Constructions |
<<<λ-cube>>> <<<λ-cube>>>
Function of Lambda calculus. \( λ x y.x^2 + y^3 \) ^^ ^ ^
| \__parameter \___parameter\__variable | ||
\__variable | ||
(_____) | ||
\___BODY | ||
---|---|---|
(___) \____HEAD
<<<Lambda abstraction>>>
Lambda function that is not binded to any name.
<<<Anonymous lambda function>>>
Replace sequenced lambda functions into single function taking sequence/product of values as argument.
SCHT: <2020-05-21 Thu>
Equation of a parameter to a bound variable, then reducing parameter from the head.
<<<β reduction>>> <<<Beta-reduction>>> <<<Beta reduction>>>
SCHT: <2020-05-10 Sun>
No beta reduction is possible.
<<<β normal from>>> <<<Beta normal form>>> <<<Beta-normal form>>>
SCHT: <2020-05-09 Sat>
Extends the Curry–Howard correspondence to the proofs in the full intuitionistic predicate calculus (includes proofs of quantified statements). Type theory, typed programming language, and constructivism (phylosophy) foundation for mathematics. Directly relates to Coq programming language.
<<<<<<CoC>>>>>>
SCHT: <2020-08-08 Sat>
Equivalence of {First-order logic, computer programming, Category theory}. They represent each-other, possible in one - possible in the other, so all the definitions and theorems have analogues in other two.
Gives a ground to the equivalence of computer programs and mathematical proofs.
Lambek added analogue to Cartesian closed category, which can be used to model logic and type theory.
Logic | Type | Category |
---|---|---|
True | () (any inhabited type) | Terminal |
False | Void | Initial |
a ∧ b | (a, b) | a × b |
a ∨ b | (a | b) | a | b |
a ⇒ b | a → b | ba |
Algebra correspondence to types:
\( ab \ + \ c \) ~ ( b | c \to a)
\( ab × ac \) ~ (b \to a, c \to a)
\( ab^{c }\) ~ (c \to b \to a)
\( ab × c \) ~ ((b, c) \to a)
<<<Curry–Howard isomorphism>>> <<<Curry-Howard-Lambek>>>
SCHT: <2020-07-05 Sun>
Translating the evaluation of a multiple argument function (or a tuple of arguments) into evaluating a sequence of functions, each with a single argument.
<<<Curry>>>
SCHT: <2020-06-24 Wed>
Classical type system for lambda calculus with parametric polymorphism and type inference. Types marked as polymorphic variables, which enables type inference over the code.
<<<Hindley-Milner>>> <<<Damas-Milner>>> <<<Damas–Hindley–Milner>>>
SCHT: <2020-07-22 Wed>
Take out something from a structure, make simplier.
See Beta reduction
<<<Reducible>>>
SCHT: <2020-05-26 Tue>
All β-reduction and η-abstraction are done in the expression.
<<<beta-eta normal form>>> <<<beta eta normal form>>>
SCHT: <2020-06-23 Tue>
\( (λ x.Mx) \xleftarrow[η]{} M \)
\ x -> g . f $ x
\ x -> g . f --eta-abstraction
<<<η-reduction>>> <<<η-conversion>>> <<<η abstraction>>> <<<η reduction>>> <<<η conversion>>> <<<eta-abstraction>>> <<<eta-reduction>>> <<<eta-conversion>>> <<<eta abstraction>>> <<<eta reduction>>> <<<eta conversion>>>
See Lambda calculus (Lambda terms) and Expression. In majority cases meaning some Lambda function.
SCHT: <2020-06-07 Sun>
Calculation into output value. Can have zero & more inputs.
Nullary operation.
Also see: Type constant.
SCHT: <2020-05-25 Mon>
\( ∀ (a,b) ∈ S, ∃ P(a,b)=f(a,b): S × S → S \)
<<<Binary operations>>>
SCHT: <2020-10-10 Sat>
Denotation symbol/name for the operation.
Shift operator defined by Lagrange through Differential operator. \( Tt \, = \, et{\frac{d{dx}}} \)
Shift
SCHT: <2020-09-18 Fri>
Denotation. \( \frac{d}{dx}, \, D, \, Dx, \, ∂x. \) Last one is partial.
\( et{\frac{d{dx}}} \) - Shift operator.
<<<Differential>>>
SCHT: <2020-08-06 Thu>
Form of writing of operator or function in-between variables for application.
For priorities see Fixity.
SCHT: <2020-06-15 Mon>
Declares the presedence of action of a function/operator.
Funciton application has presedence higher then all infix operators/functions (virtually giving it a priority 10).
P | L | Non | R |
---|---|---|---|
10 | F.A. | ||
9 | !! | . | |
8 | ^ ^^ ** | ||
7 | */ div | ||
6 | +- | \<> | |
5 | : , ++ | ||
4 | <$> | <comparison> elem | |
3 | <|> | && | |
2 | || | ||
1 | > >>= <&> | <=< >=> \=<< < | |
0 | $ $! seq |
Any operator lacking a fixity declaration is assumed to be infixl 9.
<<<Infixl>>> <<<Infixr>>> <<<Priority>>> <<<Precedence>>>
SCHT: <2020-07-18 Sat>
* is the value with which operation always yelds Zero value. \( zero, n ∈ C : ∀ n, zero*n=zero \)
* is distinct from Identity value.
SCHT: <2021-04-06 Tue>
Establishing equality between two objects.
Most often:
- equating variable to a value.
- equating parameter of a function to an argument (variable/value/function). This term often is equated to applying argument to a function, which includes β-reduction.
<<<Binds>>> <<<Binding>>> <<<Bindings>>>
SCHT: <2021-10-01 Fri>
Binding name to expression.
SCHT: <2020-05-11 Mon>
Sort-out & send.
SCHT: <2020-09-18 Fri>
For FP see Bind.
SCHT: <2020-07-09 Thu>
Bijective function from domain to itself.
Domain & permutation functions & function composition form a group.
SCHT: <2020-05-25 Mon>
Paradigm where function only describes the morphism itself.
Process of converting function to point-free. If brackets () can be changed to $ then $ equal to composition:
\ x -> g (f x)
\ x -> g $ f x
\ x -> g . f $ x
\ x -> g . f --eta-abstraction
\ x1 x2 -> g (f x1 x2)
\ x1 x2 -> g $ f x1 x2
\ x1 x2 -> g . f x1 $ x2
\ x1 -> g . f x1
<<<Pointfree>>> <<<Tacit>>> <<<Tacit programming>>>
SCHT: <2020-12-22 Tue>
(.).(.) :: (b -> c) -> (a1 -> a2 -> b) -> a1 -> a2 -> c
Composition of compositions (.).(.)
. Allows to compose-in a binary function f1(c) (.).(.) f2(a,b)
.
\ f g x y -> f (g x y)
<<<.) .>>> <<<(.).(.)>>> <<<Composition of compositions>>>
SCHT: <2020-08-09 Sun>
swing :: (((a -> b) -> b) -> c -> d) -> c -> a -> d
swing = flip . (. flip id)
swing f = flip (f . runCont . return)
swing f c a = f ($ a) c
f >>= a . b . c =<< g
SCHT: <2020-09-18 Fri>
\textgreek{πολύς} polús many
At once several forms.
In Haskell - abstract over data types.
* types:
<<<Polymorphic>>>
SCHT: <2020-06-23 Tue>
Extending polymorphism to work with unlifted and lifted types.
Abstracting over data types by parameter.
In most languages named as ‘Generics’ (generic programming).
Types:
SCHT: <2020-07-11 Sat>
Parametric polymorphism by type variables of rank-1 types.
<<<Prenex>>> <<<Prenex polymorpism>>>
SCHT: <2020-06-19 Fri>
It is property chosen for Haskell type system.
Haskell is based on Hindley-Milner type system, it is let-bound.
To have strict type inference with * - if let
and where
declarations are polymorphic - λ declarations - should be not.
See: Good: In Haskell parameters bound by lambda declaration instantiate to only one concrete type.
Constrained Parametric polymorphism.
SCHT: <2020-05-18 Mon>
Artificial constrained polymorphism dependent on incoming data type. It is interface dispatch mechanism of data types. Achieved by creating a type class instance functions.
Commonly known as overloading.
3.11.3.3.1.0.1 *<<<Ad-hoc polymorphism>>> <<<Ad hoc polymorphic>>> <<<Ad-hoc polymorphic>>> <<<Constraint>>> <<<Constraints>>>
SCHT: <2020-12-12 Sat>
* allows type τ entities with polymorphic types that can contain type τ itself. \( T = ∀ X. X → X : \; T ∈ X \vDash T ∈ T \)
The most powerful form of parametric polymorphism. See: Impredicative.
This approach has Girard’s paradox (type systems Russell’s paradox).
<<<First-class polymorphism>>>
Means that polymorphic types can apper within other types (types of function). There is a cases where higher-rank polymorphism than the a Ad hoc - is needed. For example where ad hoc polymorphism is used in constraints of several different implementations of functions, and you want to build a function on top - and use the abstract interface over these functions.
-- ad-hoc polymorphism
f1 :: forall a. MyType Class a => a -> String == f1 :: MyType Class a => a -> String
f1 = -- ...
-- higher-rank polymorphism
f2 :: Int -> (forall a. MyType Class a => a -> String) -> Int
f2 = -- ...
By moving forall
inside the function - we can achive higher-rank polymorphism.
From: https://news.ycombinator.com/item?id=8130861
Higher-rank polymorphism is formalized using System F, and there are a few
implementations of (incomplete, but decidable) type inference for it
- see e.g. Daan Leijen's research page [1] about it, or my experimental
implementation [2] of one of his papers. Higher-rank types also have some
limited support in OCaml and Haskell.
Useful example aslo a ST-Trick monad.
<<<Rank-n polymorphism>>>
Allows to declare usage of a Type and all of its Subtypes. T - Type S - Subtype of Type <: - subtype of \( S <: T = S ≤ T \)
Subtyping is: If it can be done to T, and there is subtype S - then it also can be done to S. \( S <:T : \; fT → X ⇒ fS → X \)
SCHT: <2020-05-09 Sat>
Is a lot like Subtype polymorphism, but alings itself on allowence (with | r) of subtypes and types with requested properties.
printX :: { x :: Int | r } -> String
printX rec = show rec.x
printY :: { y :: Int | r } -> String
printY rec = show rec.y
-- type is inferred as `{x :: Int, y :: Int | r } -> String`
printBoth rec = printX rec ++ printY rec
Achieved using a phantom type argument in the data type declaration.
;; * -> *
data Proxy a = ProxyValue
Then, by default the data type can be inhabited and fully work being partially defined. But multiple instances of kind polymorphic type can be distinguished by their particular type.
Example is the Proxy type:
data Proxy a = ProxyValue
let proxy1 = (ProxyValue :: Proxy Int) -- * :: Proxy Int
let proxy2 = (ProxyValue :: Proxy a) -- * -> * :: Proxy a
Leverages linear types. For exampe - if fold over a dynamic array:
- In basic Haskell - array would be copied at every step.
- Use low-level unsafe functions.
- With Linear type function we guarantee that the array would be used only at one place at a time.
So, if we use a function (* -o * -o -o *) in foldr - the fold will use the initial value only once.
SCHT: <2020-06-21 Sun>
Complex expression is determined by the constituent expressions and the rules used to combine them.
If the meaning fully obtainable form the parts and composition - it is full, pure compositionality.
If there exists composed idiomatic expression - it is unfull, unpure compositionality, because meaning leaks-in from the sources that are not in the composition.
<<<Principe of compositionality>>> <<<Composition>>> <<<Compositional>>>
SCHT: <2021-01-18 Mon>
Given the same input return the same output. So: * expression can be replaced with its corresponding resulting value without change for program’s behavior. * functions are pure.
<<<Referentially transparent>>>
SCHT: <2020-06-24 Wed>
Philosophical study of meaning. Meaning of symbols, words.
SCHT: <2020-06-17 Wed>
Constructing proofs from axiomatic semantics, verifying procedures and their properties.
Good to solve in-point localized tasks.
Process of working with abstractions.
SCHT: <2020-06-12 Fri>
arguere make clearmake known, to prove, to shine
* - evidence, proof, statement that results systematic changes.
A value binded to the function parameter. Value/topic that the fuction would process/deal with.
Also see <<<Argument>>>.
<<<Function argument>>>
Means it:
- Can be used as value.
- Passed as an argument.
From 1&2 -> it can include itself.
SCHT: <2020-08-12 Wed>
Relationship between two objects. By default it is not directed and not limited. In Set theory: some subset of a Cartesian product between sets of objects.
<<<Relations>>> <<<Relationship>>>
SCHT: <2020-08-15 Sat>
A grammar (set of production rules) that describe all possible properly composed expressions in a formal language.
Term is invented by Noam Chomsky.
<<<CFG>>>
Method that demonstrates object existance by showing the process of its creation.
SCHT: <2020-07-02 Thu>
Construction of objects, that describe/tag the meanings. In Haskell often abstractions that are ment (denotations), implemented directly in the code, sometimes exist over the code - allowing to reason and implement.
* are composable.
Good to achive more broad approach/meaning.
Also see Abstraction.
SCHT: <2020-11-23 Mon>
abs away from, off (in absentia)
tractus draw, haul, drag
Purified generalization.
Forgeting the details (axiomatic semantics). Simplified approach. Out of sight - out of mind.
* creates a new semantic level in which one can be absolutely precise (operational semantics).
It is a great did to name an abstraction (denotational semantics).
The ideal abstractions are:
- integrative (global):
- nothing, void, emptiness - “none”, initial object
- everything - “all”, “existance”, terminal object
- differential (local):
- point - “this”, “is”, “one”, stasis
- chaos - “any”, “of”, “many”, process
They are ideal - because they are the basis, the beginning. Because you can not express any other obstractions without these.
\additional
This is personal idea & the thought of autor of the book regarding basic abstractions particularly. Other definitions in the book basing on this are the proof that statement has some ground truth in it. There is ongoing philosophical discussion on the topics like these.
<<<Abstractions>>> <<<Abstracting>>> <<<Abstract>>>
Abstraction that leaks details that it is supposed to abstract away.
<<<Leaky abstractions>>>
SCHT: <2020-05-02 Sat>
Absolute abstraction.
Point that additionally can have properties.
Often abstracts something, that is why it exposes external properties on abstracting something, for example some structure, maybe mathematical. In this book objects represent algebraic structures, as we are talking about Haskell and Category theory.
Objects without process are in constant state.
<<<Structure>>> <<<Structures>>> <<<Objects>>>
Second level of absolute abstraction.
Arrow.
Can have target, can have source. Both often are objects.
Often abstracts process.
Can have properties.
Also alias in Category Theory for “morphism”, thou theory emposes properties.
3.14.2.1.3.2.1 * <<<Arrows>>> <<<Process>>>SCHT: <2020-06-07 Sun>
One that recieves unique arrow from every object.
\( ∃ ! : x → 1 \ | \ ∃ 1 ∈ \mathcal{C}, \ ∀ x ∈ \mathcal{C}\)
* is an empty sequence ()
in Haskell.
Called a unit, so recieves terminal or unit arrow.
Dual of initial object.
Denotation:
Category theory \( 1 \)
Haskell
()
SCHT: <2020-11-21 Sat>
One that emits unique arrow into every object.
\( ∃ ! : \varnothing → x \ | \ ∃ \varnothing ∈ \mathcal{C}, \ ∀ x \mathcal{C} \)
If initial object is Void
(most frequently) - emitted arrows called absurd, because they can not be called.
Dual of terminal object.
Denotation:
Category theory: \( \varnothing \)
Haskell:
Void
SCHT: <2020-05-01 Fri>
What object abstracts. Without any object external structure (aka identity in Category Theory). So * is immutable. Such herecy is called “Value semantics” and leads such things as referential transparency, functional programming and Haskell.
(Except, when you hack Haskell with explicit low-level funсtions, and start to directly mute values - then you are on your own, Haskell paradigm does not expect that.)
3.14.2.1.3.5.1 * Value semantics ValuesSCHT: <2021-01-01 Fri>
Object existing out of planes, thus it can translate objects from one plane into another. * can be tried to be described with knowledge existing inside planes (from projection on the plane), but representation would always be partial.
Tensor of rank 1 is a vector.
Translations with tensor can be seen as functors.
3.14.2.1.3.6.1 *<<<Tensors>>> <<<Tensorial>>>
SCHT: <2020-06-21 Sun>
ambi both
\textgreek{γράμμα} grámma written character
Object that from different points of view has the same meaning.
While this word has two contradictory diametrically opposite usages, one was chosen (more frequent).
But it has… Both.
TODO: For merit of differentiating the meaning about different meaning referring to Tensor as object with many meanings.
SCHT: <2020-08-26 Wed>
Two of something.
arbitrarius uncertain
Random, any one of.
Used as: Any one with this set of properties. (constraints, type, etc.).
When there is a talk about any arbitrary value - in fact it is a talk about the generalization of computations over the set of properties.
One that has an option to fail.
One that can not fail.
SCHT: <2020-06-15 Mon>
Broader parent class.
SCHT: <2020-06-30 Tue>
Represents existence. Denoted as empty sequence.
()
Type ()
holds only self-representation constructor ()
, & constructor holds nothing.
Haskell code always should recieve something back, hense nothing, emptiness, void can not be theoretically addressed, practically constructed or recieved - unit in Haskell also has a role of a stub in place of emptiness, like in IO ()
.
Takes no entries (for example has the arity of zero). Has the trivial domain.
SCHT: <2020-08-18 Tue>
Tree of syntactic elements (each node denotes construct occurring in the language/source code) that represent the full particular composed expression/implementation.
“Abstract” since does not represent every detail of the syntax (ex. parentheses), but rather concentrates on structure and content.
Widely used in compilers to check the code structure for accuracy and coherence.
<<<AST>>>
An ordered, rooted syntax tree that represents the syntactic structure of a string according to some context-free grammar.
“Concrete” since (in contrast to “abstract”) - concretely reflects the syntax of the input language.
<<<Parse tree>>> <<<Derivation tree>>>
* an infinite sequence that forgets previous objects, and remembers only currently relevant objects.
\( E \ | \ X → (X × A + 1) \), the set (or object) of streams on A (final coalgebra \( A* \) of \( E \)).
cycle
is one of stream functions.
a = (cycle [Nothing, Nothing, Just "Fizz"])
b = (cycle [Nothing, Nothing, Nothing, Nothing, Just "Buzz"])
Can be:
- indexed, timeless, with current object
- timed:
** [(timescale, event)]
** [(realtime, event)]
Has amalgamation with Functional Reactive Programming.
Values consumed once or not used.
x^2
consumes/uses x
two times (x*x)
.
<<<Linearity>>>
SCHT: <2020-08-11 Tue>
Non-self-referencing definition.
\additional
Antonym - Impredicative.
SCHT: <2020-08-23 Sun>
Specifies the quantity of specimens.
Two most common quantifiers \( ∀ \) (Forall) and \( ∃ \) (Exists). \( ∃ ! \) - one and only one (exists only unique).
Turns predicate into statement.
<<<Quantification>>> <<<Quantifiers>>> <<<Quantified>>>
SCHT: <2020-08-16 Sun>
In Haskell type variables are always introduced with it, explicitly or implicitly.
forall
means that it will unify/fixed to any type that consumer may choose.
Permits to not infer the type, but to use any that fits. The variant depends on the LANGUAGE option used:
- ScopedTypeVariables
- RankNTypes
- ExistentialQuantification
<<<Forall>>>
SCHT: <2021-01-17 Sun>
* - something having a meaning that can not be derived from the conjoined meanings of * constituents. Meaning can be special for language speakers or human with particular knowledge.
* can also mean applicative functor, people better stop making idiom from the term “idiom”.
<<<Idioms>>> <<<Idiomatic>>>
SCHT: <2020-06-11 Thu>
Self-referencing definition.
\additional
Antonym - Predicative.
SCHT: <2020-07-01 Wed>
Empirical process of studying something complex by finding and analyzing true statements about it.
Good for examining interconnections.
Something has a property in the real world, and property always yealds an axiom (<<<law>>>) for something.
Meaningful abstraction denotation always defines through properties (axioms for that definition).
Abstraction forms nicely around the boundaries where the particular properties spread. Properties inside abstraction may have emergence effect (combination of properties result into bigger property), so in that way abstracting them simplifies outside picture, as abstraction hides plethora of internal properties and exposes only emergent properties.
In Haskell under property/law most often properties of algebraic structures.
There property testing wich does what it says.
<<<Properties>>>
Joined with a common purpose.
\( P(a,P(b,c)) ≡ P(P(a,b),c) \ | \ ∀ (a,b,c) ∈ S \),
* - the order (priority) of executions of actions can be arbitrary, as long as in the end the chain is the same - they would produce the same result. Any priority of execution of the parts of the operation chain would produce the same result, as the chain of operations is in fact flat.
Property that determines how operators of the same precedence are grouped, (in computer science also in the absence of parentheses).
In a classical general sence of * (noncommutative associativity) - operation assignes/gives some (hidden) additional meaning to the operands order (positions), and their positioning also influence the result. In commutative case the result depends only on information of the operands.
Etymology: Latin associatus past participle of associare ”join with”, from assimilated form of ad ”to” + sociare ”unite with”, from socius ”companion, ally” from PIE *sokw-yo-, suffixed form of root *sekw- ”to follow”.
In Haskell * has influence on parsing when compounds have same fixity.
<<<Associative>>> <<<Associative property>>> <<<Associativity property>>>
SCHT: <2020-05-31 Sun>
* - the operations can be done in groups the direction of actions can be from the beginning towards the end.
Example: In lambda expressions same level parts follow grouping from left to right. \( (λ x . x)(λ y . y)z ≡ ((λ x . x)(λ y . y))z \)
3.14.3.1.2.2.1 *<<<Left-associative>>>
SCHT: <2020-12-24 Thu>
* - the operations groups the actions from the end towards the beginning.
Example:
[1,2,3] = 1 : 2 : 3 : [] = 1 : (2 : (3 : []))
<<<Right-associative>>>
SCHT: <2020-06-09 Tue>
Operations can’t be chained.
Often is the case when the output type is incompatible with the input type.
3.14.3.1.2.4.1 *<<<Non-associative>>>
SCHT: <2020-08-07 Fri>
\( β\alphaσ\iotaς \) - stepping
The initial point, unreducible axioms and terms that spawn a theory. AKA see Category theory, or Euclidian geometry basis.
SCHT: <2020-05-01 Fri>
The property of basis, in which if new basis is a linear combination of the prior basis, and the change of basis inverse-proportional for the description of a Tensors in this basisis.
Denotation: Components for contravariant basis denoted in the upper indices: \( Vi = x \)
The inverse of a covariant transformation is a contravariant transformation. Good example of contravarint is: When a vector should stay absolute invariant even when basis changes, that is to say it represents the same geometrical or physical object having the same magnitude and direction as before - then those absolute invariant components relate to basis under the contravariant rule.
3.14.3.1.3.1.1 *<<<Contravariant cofunctor>>> <<<Contravariant functor>>> - More inline term is Contravariant cofunctor
SCHT: <2020-05-05 Tue>
The property of basis, in which if new basis is a linear combination of the prior basis, and the change of basis proportional for a descriptions of tensors in basisis.
Denotation: Components for covariant basis denoted in the upper indices: \( Vi = x \)
3.14.3.1.3.2.1 *<<<Covariant functor>>> <<<Covariant cofunctor>>>
SCHT: <2020-05-01 Fri>
\( ∀ (a,b) ∈ S : \; P(a,b) ≡ P(b,a) \)
All processes that are independent from one-another, but on manifastation of their results - their combination result into something (create curcomstances for something) - are commutative.
<<<Commutative>>> <<<Commutative property>>>
First application gives a result. Then same operation can be applied multiple times without changing the result. Example: Start and Stop buttons on machines.
<<<Idempotent>>> <<<Idempotency>>>
SCHT: <2020-08-18 Tue>
In algebra:
- set S
- two binary operators + ×
- \( x × (y + z) = (x × y) + (x × z) \) - × is left-distributive over +
- \( (y + z) × x = (y × x) + (z × x) \) - × is right-distributive over +
- left-&right-distributive - × is distributive over +
If × has commutative property - it is two-side distributive over +.
<<<Distributive>>>
Observable action.
When systems have exact external behaviour so for observer they are the same.
Binary relation between state transition systems that match each other’s moves.
<<<Bisimilar>>>
Operation that is axiomatic (can’t be expressed from other given axioms of the system).
In program languages it is most probably implemented by lower-level programming.
In Haskell they are provided by GHC.
More: GHC Wiki/prim-ops.
<<<PrimOps>>>
SCHT: <2020-08-02 Sun>
Words that name objects of reality and their qualities.
SCHT: <2021-01-05 Tue>
Meaning | Greek prefix | Latin prefix |
---|---|---|
above, excess | hyper- | super-, ultra- |
across, beyond, through | dia- | trans- |
after | post- | |
again, back | re- | |
against | anti- | contra-, (in-, ob-) |
all | pan | omni- |
around | peri- | circum- |
away or from | apo-, ap- | ab- (or de-) |
bad, difficult, wrong | dys- | mal- |
before | pro- | ante-, pre- |
between, among | inter- | |
both | amphi- | ambi- |
completely or very | de-, ob- | |
down | de-, ob- | |
four | tetra- | quad- |
good | eu- | ben-, bene- |
half, partially | hemi- | semi- |
in, into | en- | il-, im-, in-, ir- |
in front of | pro- | pro- |
inside | endo- | intra- |
large | macro- | (macro-, from Greek) |
many | poly- | multi- |
not* | a-, an- | de-, dis-, in-, ob- |
on | epi- | |
one | mono- | uni- |
out of | ek- | ex-, e- |
outside | ecto-, exo- | extra-, extro- |
over | epi- | ob- (sometimes) |
self | auto-, aut-,auth- | ego- |
small | micro- | |
three | tri- | tri- |
through | dia- | trans- |
to or toward | epi- | ad-, a-, ac-, as- |
two | di- | bi- |
under, insufficient | hypo- | sub- |
with | sym-, syn- | co-. com-, con- |
within, inside | endo- | intra- |
without | a-, an- | dis- (sometimes) |
<<<Greek prefix>>> <<<Latin prefix>>>
SCHT: <2021-01-02 Sat>
Well-defined collection of distinct objects.
<<<Sets>>> <<<Set theory>>>
\( {\displaystyle ∀ X\left[\varnothing ∉ X\implies ∃ f\colon X→ \bigcup X\quad ∀ A∈ X\,(f(A)∈ A)\right]} \)
Simple version:
For any inhabited sets, exists a set with exactly one element in common with each of them.
… from more wide-known variant:
Given any set X of pairwise disjoint non-empty sets, there exists at least one set C that contains exactly one element in common with each of the sets in X.
Most official formalization:
For any set X of nonempty sets, there exists a choice function f defined on X.
SCHT: <2020-06-03 Wed>
- Set which complements an open set.
- Is form of Closed-form expression. Set can be closed in under a set of operations.
SCHT: <2020-08-05 Wed>
For some set \( \mathcal{S} \), the power set (\( \mathcal{P(S)} \)) is a set of all subsets of \( \mathcal{S} \), including \( \{\} \) & \( \mathcal{S} \) itself.
Denotation: \( \mathcal{P(S)} \)
SCHT: <2020-05-28 Thu>
Singleton - unit set - set with exactly one element. Also 1-sequence.
If there exists normal set of all sets - it should contain itself, which makes it abnormal.
SCHT: <2020-07-15 Wed>
\( \mathcal{A} × \mathcal{B} ≡ ∑∀{(a,b)} \ | \ ∀ a ∈ \mathcal{A}, ∀ b ∈ \mathcal{B} \). Operation, returns a set of all ordered pairs \( (a, b) \)
Any function, functor is a subset of Cartesian product.
\( ∑{(elem ∈ (\mathcal{A} × \mathcal{B}))} = cardinalityA × B \)
Properties:
- not associative
- not commutative
SCHT: <2020-05-01 Fri>
Subset of the cartesian product of two sets.
<<<Pullbacks>>>
Modern set theory. Axiomatic system free of paradoxes such as Russell’s paradox and at the same time preserves the logical language of scientific works.
<<<ZFC>>>
Since property yealds the according law, family of unit tests for the property can be abstracted into the function that test the law.
Unit test cases come from generator, and test the law empirically, but repeatedly and automatically.
Property corresponds to the according law. In property testing you need to think additionally about generator and shrinking.
Exhaustive | Randomized | Unit test (Single sample) | |
---|---|---|---|
Whole set of values | Exhaustive property test | Randomised property test | One element of a set |
Special subset of values | Exhaustive specialised property test | Randomised specialised property test | One element of a set |
Seed
|
v
Gen A -> A
^
|
Size
Seed allows reproducibility. There is anyway a need to have some seed. Size allows setting upper bound on size of generated value. Think about infinity of list.
After failed test - shrinking tests value parts of contrexample, finds a part that still fails, and recurses shrinking.
<<<Generators>>>
When sertain theorem only works for a specific set of values - the according generator needs to be produced.
arbitrary :: Arbitrary a => Gen a
suchThat :: Gen a -> (a -> Bool) -> Gen a
elements :: [a] -> Gen a
Often it is convinient to abstract testing of same function properties:
It can be done with (aka TestSuite combinator):
-- Definition
{-# LANGUAGE ScopedTypeVariables #-}
{-# LANGUAGE AllowAmbiguousTypes #-}
eqSpec :: forall a. Arbitrary a => Spec
-- Usage
{-# LANGUAGE TypeApplications #-}
spec :: Spec
spec = do
eqSpec @Int
Eq Int
(==) :: Int -> Int -> Bool
is reflexive
is symetric
is transitive
is equivalent to (\ a b -> not $ a /= b)
(/=) :: Int -> Int -> Bool
is antireflexive
is equivalent to (\ a b -> not $ a == b)
Commutativity
:: Arbitrary a => (a -> a -> a) -> Property
Symmetry
:: Arbitrary a => (a -> a -> Bool) -> Property
Equivalence
:: (Arbitrary a, Eq b) => (a -> b) -> (a -> b) -> Property
:: (Arbitrary a, Eq b) => (a -> b) -> (b -> a) -> Property
Target
is a member of the Arbitrary type class.
Target -> Bool
is something Testable
. This properties can be complex.
Generator arbitrary
gets the seed, and produces values of Target
.
Function quickCheck
runs the loop and tests that generated Target
values always comply the property.
import Test.QuickCheck
import Test.QuickCheck.Function
import Test.QuickCheck.Property.Common
import Test.QuickCheck.Property.Functor
import Test.QuickCheck.Property.Common.Internal
data Four' a b = Four' a a a b
deriving (Eq, Show)
instance Functor (Four' a) where
fmap f (Four' a b c d) = Four' a b c (f d)
instance (Arbitrary a, Arbitrary b) => Arbitrary (Four' a b) where
arbitrary = do
a1 <- arbitrary
a2 <- arbitrary
a3 <- arbitrary
b <- arbitrary
return (Four' a1 a2 a3 b)
-- Wrapper around `prop_FunctorId`
prop_AutoFunctorId :: Functor f => f a -> Equal (f a)
prop_AutoFunctorId = prop_FunctorId T
type Prop_AutoFunctorId f a
= f a
-> Equal (f a)
-- Wrapper around `prop_AutoFunctorCompose`
prop_AutoFunctorCompose :: Functor f => Fun a1 a2 -> Fun a2 c -> f a1 -> Equal (f c)
prop_AutoFunctorCompose f1 f2 = prop_FunctorCompose (applyFun f1) (applyFun f2) T
type Prop_AutoFunctorCompose structureType origType midType resultType
= Fun origType midType
-> Fun midType resultType
-> structureType origType
-> Equal (structureType resultType)
main = do
quickCheck $ eq $ (prop_AutoFunctorId :: Prop_AutoFunctorId (Four' ())Integer)
quickCheck $ eq $ (prop_AutoFunctorId :: Prop_AutoFunctorId (Four' ()) (Either Bool String))
quickCheck $ eq $ (prop_AutoFunctorCompose :: Prop_AutoFunctorCompose (Four' ()) String Integer String)
quickCheck $ eq $ (prop_AutoFunctorCompose :: Prop_AutoFunctorCompose (Four' ()) Integer String (Maybe Int))
- Pick the right language/stack to implement features.
- How expensive breakage can be.
- Pick the right tools to test this.
Process of reducing coplexity in the test case - re-run with smaller values and make sure that the test still fails.
SCHT: <2020-07-08 Wed>
Purely abtract & theoretical logical object (idea) that has a Boolean value.
* is expressed by a statement.
<<<Propositions>>>
SCHT: <2020-06-01 Mon>
Logically undividable unit. Does not contain logical connectives.
Often abstracts the non-logical (“real”) objects.
<<<Atomic propositions>>>
Formed by connecting propositions by logical connectives.
<<<Compound propositions>>>
Studies propositions and argument flow.
Distinquishes logically indivisible units (atomic propositions) and abstracts them as variable and constant values of Boolean type properties. Studies consequences of those value aguments (atomic proposition) on composed propositions.
Invented by Aristotle.
Classical system that lead humanity to profound advancement. The classical * language thou is limited and so in modern day extensions (mainly First-order logic) are used in the sciences.
Not Turing-complete, for example it is impossible to construct an arbitrary loop.
<<<Proposition logic>>> <<<Proposition calculus>>> <<<Propositional calculus>>> <<<Statement logic>>> <<<Sentential logic>>> <<<Sentential calculus>>> <<<Zeroth-order logic>>>
SCHT: <2020-11-08 Sun>
Extension of a propositional logic that adds quantifiers.
Turing-complete.
<<<Predicate logic>>> <<<First-order predicate logic>>> <<<First-order predicate calculus>>>
Extension over first-order logic that quantifies over relations.
3.17.1.4.2.2.1 <<<Higher-order logic>>>Extension over second-order logic that uses additional quantifiers, stronger semantics.
Is more expressive, but model-theoretic properties are less well-behaved.
SCHT: <2020-08-15 Sat>
Logical operation.
<<<Logical connectives>>>
SCHT: <2021-09-02 Thu>
Logical AND.
Denotation: \( ∧ \)
Multiplies cardinalities.
Haskell kind:
* *
SCHT: <2021-06-14 Mon>
Logical \( OR \) Denotation: \( ∨ \)
Summs cardinalities.
Relates to:
- (in sets) union
- (in algebra) addition
- (in categories) sum
SCHT: <2020-07-25 Sat>
Function with Boolean codomain. \( P: X → \{ true, \ false \} \) - * on \( X \).
Notation: \( P(x) \)
Im many cases includes relations, quantifiers.
SCHT: <2020-08-26 Wed>
Declarative expression that is a bearer of a proposition.
When we talk about expression or statement being true/false - in fact we refer to the proposition that they represent.
Difference between proposition, statement, expression:
- “2 + 3 = 5”
- “two plus three equals five”
- 1 & 2 are statements. Each of them is a collection of transmission symbols (linguistic objects) from a symbol systems \( ≡ \) expression. Each of them is expression that bears proposition (an idea resulting in a Boolean value) \( ≡ \) statement.
- 1 & 2 represent the same proposition. Proposition from 1 \( ≡ \) proposition from 2.
- Statement 1 \( ≠ \) statement 2. They are two different statements, written in different systems. And statement “2 + 3 = 5” \( ≠ \) statement “3 + 2 = 5”.
<<<Assertion>>> <<<Assertions>>> <<<Statements>>>
The if
(requirement) part of the proposition.
else
(consequential) part of the proposition.
Nonsensical proposition that has {impossible, not full, false} premise and as such - impossible to definitely prove true nor false (under currently given tools inside the particular theory).
Such proposition falls into paradox due to property of excluded middle in the classical logic.
Requirements of the proposition (antecedent part) cannot be satisfied.
Therefore “vacuous true/false” means: “considered as, but not proven”.
Is a good example of why Haskell uses total functions even for if .. then .. else ..
statements.
There is also vacuous
function in Haskell, see Void.
SCHT: <2020-10-08 Thu>
If and only if, exectly when, just. Denotation: \( \iff \)
Haskell structures
Are not first-class. It is a set of patter match semantic notations.
Must be linear.
* precedence (especially with more then one parameter, especially with _
used) often changes the function.
SCHT: <2020-10-11 Sun>
f list@(x, xs) = ...
f (x:xs) = x:x:xs -- Can be compiled with reconstruction of x:xs
f a@(x:_) = x:a -- Reuses structure without reconstruction
<<<As-patterns>>> <<<As pattern>>> <<<As patterns>>>
Matches anything and can not be binded. For matching someting that should pass not checked and is not used.
head (x:_) = x
tail (_:xs) = xs
<<<Wild-cards>>> <<<Wildcard>>> <<<Wildcards>>>
SCHT: <2020-10-09 Fri>
case x of
pattern1 -> ex1
pattern2 -> ex2
pattern3 -> ex3
otherwise -> exDefault
Bolting guards & expressions with syntatic sugar on case:
case () of _
| expr1 -> ex1
| expr2 -> ex2
| expr3 -> ex3
| otherwise -> exDefault
Pattern matching in function definitions is realized with case expressions.
Check values against the predicate and use the first match definition:
f x
| predicate1 = definition1
| predicate2 = definition2
...
| x < 0 = definitionN
...
| otherwise = definitionZ
<<<Guards>>>
SCHT: <2020-06-26 Fri>
Allows check a list of pattern matches against functions, and then proceed.
(patternMatch1) <- (funcCheck1) |
, (patternMatch2) <- (funcCheck2) = RHS
lookup :: Eq a => a -> [(a, b)] -> Maybe b
addLookup l a1 a2
| Just b1 <- lookup a1 l
, Just b2 <- lookup a2 l
= b1 + b2
{-...other equations...-}
Run functions, they must succeed. Then pattern match results to b1
, b2
. Only if successful - execute the equation.
Default in Haskell 2010.
<<<Pattern guards>>>
Defers the pattern match directly to the last moment of need during execution of the code.
f (a, b) = g a b -- It would be checked that the pattern of the pair constructor
-- is present, and that parameters are present in the constructor.
-- Only after that success - work would start on the RHS, aka then construction
-- g would start only then.
f ~(a, b) = g a b -- Pattern match of (a, b) deferred to the last moment,
-- RHS starts, construction of g starts.
-- For this lazy pattern the equivalent implementation would be:
-- f p = g (fst p) (snd p) -- RHS starts, during construction of g
-- the arguments would be computed and found, or error would be thrown.
Due to full laziness deferring everything to the runtime execution - the lazy pattern is one-size-fits all (irrefutable), analogous to _
, and so it does not produce any checks during compilation, and raises errors during runtime.
* is very useful during recursive construction of recursive structure/process, especially infinite.
<<<Lazy-pattern>>> <<<Lazy patterns>>>
Entire LHS is a pattern, is a lazy pattern.
fib@(1:tfib) = 1 : 1 : [ a+b | (a,b) <- zip fib tfib ]
<<<Pattern bindings>>>
SCHT: <2020-09-18 Fri>
Process/code placing extra rules & constraints on the construction of values.
SCHT: <2020-09-20 Sun>
There are these levels of Haskell code:
<<<Code level>>>
Level of code that works with data types.
type ...
newtype ...
data ...
class ...
instance ...
<<<Type level declarations>>> <<<Type-level declaration>>> <<<Type-level declarations>>>
if
The type level information is complete (strongly connected graph)
then
Generalize the types and check if type level consistent to term level.
else
Infer the missing type level part from the term level. There are certain situations and structures where ambiguity arises and is unsolvable from the information of the term level (most basic example is polymorphic recursion).
<<<Typecheck>>> <<<Typechecking>>> <<<Typechecks>>>
SCHT: <2020-05-01 Fri>
Type level declaration is considered to “have a CUSK” is it has enough syntatic information to warrant completeness (strongly connected graph) and start checking type level correspondence to term level, it is a ad-hock state ot type inferring.
In the future GHC would use other algorythm over/instead of CUSK.
3.18.4.2.2.2.1 *<<<CUSK>>> <<<CUSKs>>> <<<Complete user-specific kind signatures>>> <<<Complete, user-specific kind signature>>>
SCHT: <2020-09-18 Fri>
Level of code that does logical execution.
SCHT: <2020-09-20 Sun>
Level of code, about compilation processes/results.
<<<Compilation level>>>
SCHT: <2020-07-23 Thu>
Level of code of main program operation, when machine does computations with compiled binary code.
Level of code where kinds & kind declarations are situated, infered and checked.
Applying the type check to kind check:
if
The kind level information is complete (strongly connected graph)
then
Check if kind level consistent to term level.
else
Infer the missing kind level parts from the type level. There are certain situations and structures where ambiguity arises and is unsolvable from the information of the kind level.
With StandaloneKindSignatures
kind completeness happens against found (standalone) kind signature.
With CUSKs
extension <<<kind>>> completeness happens agains “complete user-specific kind signature”
<<<Kindcheck>>> <<<Kind checks>>>
SCHT: <2020-12-27 Sun>
Instance which is separated from one of {type, class| implemetations.
Situation when for some publically used type the upstream module provides type class but does not provide an instance.
That allows/pushes to implement own version of instance.
If upstream would add instance - now both upstream instance and downstream instances exist. Locally that would create instance clash. Remotely, through modules usage - that should create inconsistancy problems in computations, since instances may not be bisimilar.
If module has any orphans - then in GHC terms all module is tagged an “orphan module”. By the situation GHC on compiling some module is required to always visits the every interface file of every orphan module below the module being compiled. This is usually a wasted work which nevertheless is required. Have as few orphan modules as possible” (“GHC User’s Guide Documentation, Release 8.8.3”). Orphans prolong the compilation of the project and al dependent downstream code.
See: Good: Handling orphan instance.
SCHT: <2020-08-04 Tue>
Placeholder value that helps to do typechecking.
Hierarchical naming scheme:
Algebra -- Was this ever used?
DomainConstructor -- formerly DoCon
Geometric -- formerly BasGeomAlg
Codec -- Coders/Decoders for various data formats
Audio
Wav
MP3
...
Compression
Gzip
Bzip2
...
Encryption
DES
RSA
BlowFish
...
Image
GIF
PNG
JPEG
TIFF
...
Text
UTF8
UTF16
ISO8859
...
Video
Mpeg
QuickTime
Avi
...
Binary -- these are for encoding binary data into text
Base64
Yenc
Control
Applicative
Arrow
Exception -- (opt, inc. error & undefined)
Concurrent -- as hslibs/concurrent
Chan -- these could all be moved under Data
MVar
Merge
QSem
QSemN
SampleVar
Semaphore
Parallel -- as hslibs/concurrent/Parallel
Strategies
Monad -- Haskell 98 Monad library
ST -- ST defaults to Strict variant?
Strict -- renaming for ST
Lazy -- renaming for LazyST
State -- defaults to Lazy
Strict
Lazy
Error
Identity
Monoid
Reader
Writer
Cont
Fix -- to be renamed to Rec?
List
RWS
Data
Binary -- Binary I/O
Bits
Bool -- &&, ||, not, otherwise
Tuple -- fst, snd
Char -- H98
Complex -- H98
Dynamic
Either
Int
Maybe -- H98
List -- H98
PackedString
Ratio -- H98
Word
IORef
STRef -- Same as Data.STRef.Strict
Strict
Lazy -- The lazy version (for Control.Monad.ST.Lazy)
Binary -- Haskell binary I/O
Digest
MD5
... -- others (CRC ?)
Array -- Haskell 98 Array library
Unboxed
IArray
MArray
IO -- mutable arrays in the IO/ST monads
ST
Trees
AVL
RedBlack
BTree
Queue
Bankers
FIFO
Collection
Graph -- start with GHC's DiGraph?
FiniteMap
Set
Memo -- (opt)
Unique
Edison -- (opt, uses multi-param type classes)
Prelude -- large self-contained packages should have
Collection -- their own hierarchy? Like a vendor branch.
Queue -- Or should the whole Edison tree be placed
Database
MySQL
PostgreSQL
ODBC
Dotnet
... -- Mirrors the MS .NET class hierarchy
Debug -- see also: Test
Trace
Observe -- choose a default amongst the variants
Textual -- Andy Gill's release 1
ToXmlFile -- Andy Gill's XML browser variant
GHood -- Claus Reinke's animated variant
Foreign
Ptr
StablePtr
ForeignPtr -- rename to FinalisedPtr? to void confusion with Foreign.Ptr
Storable
Marshal
Alloc
Array
Errors
Utils
C
Types
Errors
Strings
GHC
Exts -- hslibs/lang/GlaExts
...
Graphics
HGL
Rendering
Direct3D
FRAN
Metapost
Inventor
Haven
OpenGL
GL
GLU
Pan
UI
FranTk
Fudgets
GLUT
Gtk
Motif
ObjectIO
TkHaskell
X11
Xt
Xlib
Xmu
Xaw
Hugs
...
Language
Haskell -- hslibs/hssource
Syntax
Lexer
Parser
Pretty
HaskellCore
Python
C
...
Nhc
...
Numeric -- exports std. H98 numeric type classes
Statistics
Network -- (== hslibs/net/Socket), depends on FFI only
BER -- Basic Encoding Rules
Socket -- or rename to Posix?
URI -- general URI parsing
CGI -- one in hslibs is ok?
Protocol
HTTP
FTP
SMTP
Prelude -- Haskell98 Prelude (mostly just re-exports
other parts of the tree).
Sound -- Sound, Music, Digital Signal Processing
ALSA
JACK
MIDI
OpenAL
SC3 -- SuperCollider
System -- Interaction with the "system"
Cmd -- ( system )
CPUTime -- H98
Directory -- H98
Exit -- ( ExitCode(..), exitWith, exitFailure )
Environment -- ( getArgs, getProgName, getEnv ... )
Info -- info about the host system
IO -- H98 + IOExts - IOArray - IORef
Select
Unsafe -- unsafePerformIO, unsafeInterleaveIO
Console
GetOpt
Readline
Locale -- H98
Posix
Console
Directory
DynamicLinker
Prim
Module
IO
Process
Time
Mem -- rename from cryptic 'GC'
Weak -- (opt)
StableName -- (opt)
Time -- H98 + extensions
Win32 -- the full win32 operating system API
Test
HUnit
QuickCheck
Text
Encoding
QuotedPrintable
Rot13
Read
Lex -- cut down lexer for "read"
Show
Functions -- optional instance of Show for functions.
Regex -- previously RegexString
Posix -- Posix regular expression interface
PrettyPrint -- default (HughesPJ?)
HughesPJ
Wadler
Chitil
...
HTML -- HTML combinator lib
XML
Combinators
Parse
Pretty
Types
ParserCombinators -- no default
ReadP -- a more efficient "ReadS"
Parsec
Hutton_Meijer
...
Training -- Collect study and learning materials
<name of the tutor>
<<<Top-level module name>>> <<<Top-level module names>>>
Haskell has special meaning for:
case, class, data, deriving, do,else, if, import,
in, infix, infixl, infixr, instance, let,
of, module, newtype, then, type, where
<<<Reserved words>>>
SCHT: <2020-05-01 Fri>
import
statement by default imports identifiers from the other module, using hierarchical module name, brings into scope the identifiers to the global scope both into unqualified and qualifies by the hierarchical module name forms.
This possibilities can mix and match:
<modName> ()
- import only instances of type classes.<modName> (x, y)
- import only declared indentifiers.qualified <modName>
- discards unqialified names, forse obligatory namespace for the imports.hiding (x, y)
- skip import of declared identifies.<modName> as <modName>
- renames module namespace.<type/class> (..)
- import class & it’s methods, or type, all its data constructors & field names.
* expression is a set of cross-recursive lazy pattern bindings.
Declarations permitted:
- type signatures
- function bindings
- pattern bindings
It is an expression (macro) and that integrates in external lexical scope expression it applied in.
Form:
let
b1
bn
in
c
<<<Let expression>>> <<<Let expressions>>>
Part of the syntax of the whole function declaration, has according scope.
As part of whole declaration - can extend over definitions of the funtion (pattern matches, guards).
Form:
f match1 = y
f match2 = y
f x =
| cond1 x = y
| cond2 x = y
| otherwise = y
where
y = ... x ...
<<<Where clause>>>
Document that is a standart of language.
<<<Report>>> <<<Haskell Report>>> <<<Haskell 98 Language Report>>> <<<Haskell 98 Report>>> <<<Haskell 1998 Language Report>>> <<<Haskell 2010 Language Report>>> <<<Haskell 2010 Report>>>
Current language development mod.
<<<Haskell prime>>>
SCHT: <2020-10-24 Sat>
Library of combinators to provide Haskell (functional language without mutation) with the emulation of get
-ters and set
-ters of imperative language.
SCHT: <2020-09-20 Sun>
Pragma - instruction to the compiler that specifies how a compiler should process the code. Pragma in Haskell have form:
{-# PRAGMA options #-}
SCHT: <2020-09-20 Sun>
Controls what variations of the language are permitted. It has a set of allowed options: https://downloads.haskell.org/~ghc/latest/docs/html/users_guide/glasgow_exts.html, which can be supplied.
<<<Language options>>>
{-# LANGUAGE FlexibleContexts #-}
{-# LANGUAGE FlexibleInstances #-}
{-# LANGUAGE InstanceSigs #-}
{-# LANGUAGE MultiParamTypeClasses #-}
{-# LANGUAGE BlockArguments #-}
{-# LANGUAGE LambdaCase #-}
{-# LANGUAGE EmptyCase #-}
{-# LANGUAGE OverloadedStrings #-}
{-# LANGUAGE TypeApplications #-}
SCHT: <2020-09-16 Wed>
Allow type signatures which appear that they would result in an unusable binding. However GHC will still check and complain about a functions that can never be called.
Enables an alternative in-depth reduction that translates the do-notation to the operators <$>
, <*>
, join
as far as possible.
For GHC to pickup the patterns, the final statement must match one of these patterns exactly:
pure E
pure $ E
return E
return $ E
When the statements of do expression have dependencies between them, and ApplicativeDo cannot infer an Applicative type - GHC uses a heuristic \( O(n^2) \) algorithm to try to use <*> as much as possible. This algorithm usually finds the best solution, but in rare complex cases it might miss an opportunity. There is aslo \( O(n^3) \) algorithm that finds the optimal solution: -foptimal-applicative-do
.
Requires ap = <*>
, return = pure
, which is true for the most monadic types.
- Allows use of do-notation with types that are an instance of Applicative and Functor
- In some monads, using the applicative operators is more efficient than monadic bind. For example, it may enable more parallelism.
The only way it shows up at the source level is that you can have a do
expression with only Applicative or Functor constaint.
It is possible to see the actual translation by using -ddump-ds
.
SCHT: <2020-05-01 Fri>
Enable the definition of further constraints on individual class methods.
SCHT: <2020-05-01 Fri>
Enable C preprocessor.
SCHT: <2020-10-20 Tue>
Automatic deriving of instances for the Functor type class. For type power set functor is unique, its derivation inplementation can be autochecked.
SCHT: <2020-09-18 Fri>
Allow explicit forall quantificator in places where it is implicit by Haskell.
Ability to use complex constraints in class declaration contexts. The only restriction on the context in a class declaration is that the class hierarchy must be acyclic.
class C a where
op :: D b => a -> b -> b
class C a => D a where ...
\( C :> D \), so in C we can talk about D.
Synergizes with ConstraintKinds.
SCHT: <2020-07-16 Thu>
Allow type class instances types contain nested types.
instance C (Maybe Int) where ...
Implies TypeSynonymInstances.
SCHT: <2020-08-07 Fri>
Enable GHC’s newtype
cunning generalised deriving mechanism.
newtype Dollars = Dollars Int
deriving (Eq, Ord, Show, Read, Enum, Num, Real, Bounded, Integral)
(In old Haskell 98 only Eq, Ord, Enum could been inherited.)
SCHT: <2020-07-04 Sat>
Allow definition of functions expecting implicit parameters. In the Haskell that has static scoping of variables allows the dynamic scoping, such as in classic Lisp or ELisp. Sure thing this one can be puzzling as hell inside Haskell.
SCHT: <2021-03-17 Wed>
Enables expressions of the form:
\case { p1 -> e1; ...; pN -> eN }
-- OR
\case
p1 -> e1
...
pN -> eN
Implies: ConstrainedClassMethods Enable the definitions of typeclasses with more than one parameter.
class Collection c a where
Multiparameter generalizes type classes with interpretation of them being relations on types.
SCHT: <2020-08-05 Wed>
Enable multi-way-if syntax.
if | guard1 -> code1
| ...
| guardN -> codeN
SCHT: <2020-07-26 Sun>
Enable overloaded string literals (string literals become desugared via the IsString
class).
With overload, string literals has type:
(IsString a) => a
The usual string syntax can be used, e.g. ByteString
, Text
, and other variations of string-like types.
Now they can be used in pattern matches as char->integer
translations. To pattern match Eq
must be derived.
To use class IsString
- import it from GHC.Ext
.
Partial type signature containins wildcards, placeholders (_
, _name
).
Allows programmer to which parts of a type to annotate and which to infer. Also applies to constraint part.
As untuped expression, partly typed can not polymorphicly recurse.
-Wno-partial-type-signatures supresses infer warnings.
SCHT: <2020-05-31 Sun>
Enable types of arbitrary rank. See Type rank.
Implies ExplicitForAll.
Allows forall
quantifier:
- Left side of →
- Right side of →
- as argument of a constructor
- as type of a field
- as type of an implicit parameter
- used in pattern type signature of lexically scoped type variables
By default type variables do not have a scope except inside type signatures where they are used.
Extension allows:
- explicitly
forall
quantified type variables broad the scope to the internals of implementation. - pattern type signatures can use
::
to denote a type signature within a pattern.
When there are internall type signatures provided in the code block (where
, let
, etc.) they (main type description of a function and internal type descriptions) restrain one-another and become not trully polymorphic, which creates a bounding interdependency of types that GHC would complain about.
* option provides the lexical scope inside the code block for type variables that have forall quantifier. Because they are now lexiacally scoped - those type variables are used across internal type signatures.
Implies ExplicitForAll.
See: GHC documentation, explanation blogpost, typeclasses article.
SCHT: <2020-09-18 Fri>
Allow tuple section syntax:
(, True)
(, "I", , , "Love", , 1337)
SCHT: <2020-06-25 Thu>
Allow type application syntax:
read @Int 5
:type pure @[]
pure @[] :: a -> [a]
:type (<*>) @[]
(<*>) @[] :: [a -> b] -> [a] -> [b]
--
instance (CoArbitrary a, Arbitrary b) => Arbitrary (a -> b)
λ> ($ 0) <$> generate (arbitrary @(Int -> Int))
SCHT: <2020-06-20 Sat>
Now type synonim can have it’s own type class instances.
Permit instances which may lead to type-checker non-termination.
GHC has Instance termination rules regardless of FlexibleInstances FlexibleContexts.
SCHT: <2020-05-23 Sat>
foo (f1 -> Pattern1) = c1
foo (fn -> Pattern2 a b) = g1 a b
(expression → pattern): take what is came to match - apply the expression, then do pattern-match, and return what originally came to match.
Semantics:
- expression & pattern share the scope, so also variables.
- if (=(expression :: t1 -> t2) && (pattern
- t2)=)
then
(ViewPattern
(/expression/ -> /pattern/)
:: t1
) (return what originally was recieved into pattern match) else skip
* are like pattern guards that can be nested inside of other patterns. * are a convenient way to pattern-match algebraic data type.
Additional possible usage:
foo a (f2 a -> Pattern3 b c) = g2 b c -- only for function definitions
foo ((f,_), f -> Pattern4) = c2 -- variables can be bount to the left in data constructors and tuples
SCHT: <2021-02-07 Sun>
Allow contexts in data types.
data Eq a => Set a = NilSet | ConsSet a (Set a)
-- NilSet :: Set a
-- ConsSet :: Eq a => a -> Set a -> Set a
Considered misfeature. Deprecated. Going to be removed.
Type signatures for type-level declarations.
type <name_1> , ... , <name_n> :: <kind>
type MonoTagged :: Type -> Type -> Type
data MonoTagged t x = MonoTagged x
type Id :: forall k. k -> k
type family Id x where
Id x = x
type C :: (k -> Type) -> k -> Constraint
class C a b where
f :: a b
type TypeRep :: forall k. k -> Type
data TypeRep a where
TyInt :: TypeRep Int
TyMaybe :: TypeRep Maybe
TyApp :: TypeRep a -> TypeRep b -> TypeRep (a b)
< GHC 8.10.1 - type signatures were only for term level declarations.
Extension makes signatures feature more uniformal.
Allows to set the order of quantification, order of variables in a kind. For example when using TypeApplications.
Allows to set full kind of derivable class, solving situations with GADT return kind.
3.18.12.1.1.26.1 *<<<SAKS>>> <<<Standalone kind signatures>>>
Very healpful. Helps to solve type level, helps to establish type signatures and constraints.
Allow to provide _
in the type signatures to automatically infere-in the type information there.
Wild cards:
- Type
f :: _ -> _ -> a
- Constraint
f :: _ => a -> b -> c
- Named
f :: _x -> _x -> a
allows to identify the same wildcard.
Allow type signature to hold operator names:
data a + b = Plus a b
—
Implies ExplicitNamespaces
In libraries/ghc-boot-th/GHC/LanguageExtensions/Type.hs
add new constructor to the Extension
type
data Extension
= Cpp
| OverlappingInstances
...
| Foo
/main/DynFlags.hs
extend xFlagsDeps
:
xFlagsDeps = [
flagSpec "AllowAmbiguousTypes" LangExt.AllowAmbiguousTypes,
...
flagSpec "Foo" LangExt.Foo
]
It is for basic case. For testing, parser see further: https://blog.shaynefletcher.org/2019/02/adding-ghc-language-extension.html
SCHT: <2020-09-21 Mon>
* changing code/applying patch sneakily - and possibility incompatibility with other at runtime. Monkey patch is derivative term.
SCHT: <2020-08-24 Mon>
From Guerrilla patch.
* is a way for program to modify supporting system software affecting only the running instance of the program.
Point of mutual meeting. Code behind interface determines how data is consumed.
Importable organizational unit.
SCHT: <2021-06-14 Mon>
Area where binds are accessible.
The name resolution depends upon the program state when the name is encountered, which is determined by the execution context or calling context.
SCHT: <2020-07-07 Tue>
Scope bound by the structure of source code where the named entity is defined.
<<<Static scope>>>
SCHT: <2020-07-28 Tue>
Scope applies only in (current) area.
<<<Local>>>
SCHT: <2020-07-07 Tue>
When in the local scope bigger scope variable overriden by same name variable from the local scope.
SCHT: <2020-08-23 Sun>
Artificial way to make language easier to read and write.
SCHT: <2020-09-11 Fri>
Is parametric polymorphism in programming.
Extends the Lambda calculus by introducing \( ∀ \) (universal quantifier) over types.
<<<Girard–Reynolds polymorphic lambda calculus>>> <<<Girard-Raynolds>>>
SCHT: <2021-04-07 Wed>
Final evaluation inside the function. Produces the function result.
Not evaluated calculation. Can be dragged around, until be lazily evaluated.
Storage of | Block name |
---|---|
All not currently processing data | <<<Heap>>> |
Function call, local variables | <<<Stack>>> |
Static and global variables | Static/Global |
Instructions | Binary code |
When even Main invoked - it work in Stack, and called Stack frame. Stack frame size for function calculated when it is compiled. When stacked Stack frames exceed the Stack size - stack overflow happens.
Mathematical model of computation that defines abstract Turing machine. Abstract machine which manipulates symbols on a strip of tape, according to a table of rules.
Set of action rules that can simulate any Turing machine.
<<<Turing incomplete>>> <<<Turing incompleteness>>> <<<Turing completeness>>> <<<Computationally universal>>>
SCHT: <2020-07-21 Tue>
Read-eval-print loop, aka interactive shell.
Language design/fitted for particular domain of application. Mainly should be Turing incomplete, since general-purpose language implies Turing completeness.
<<<Domain-specific language>>> <<<DSL>>>
DSL used inside outer language.
Two levels of embedding:
- Shallow: DSL translates into Haskell directly
- Deep: Between DSL and Haskell there is a data structure that reflects the expression tree, AKA stores the syntax tree.
<<<eDSL>>>
SCHT: <2020-07-27 Mon>
Cell that values may inhabit.
(:) :: a -> [a] -> [a]
<<<Cons>>>
SCHT: <2020-07-21 Tue>
_
SCHT: <2020-07-26 Sun>
*
/ \
SCHT: <2020-07-07 Tue>
Is a chain of memory cells, each points to the both value of element and to the next memory cell.
Array:
:
/ \
1 :
/ \
2 :
/ \
3 []
1:2:3:[]
Spine:
:
/ \
_ :
/ \
_ :
/ \
_ []
Object that recieves the arrow.
Immidiate successor.
Object that sends arrow.
SCHT: <2020-06-21 Sun>
Immidiate predecessor.
SCHT: <2020-05-01 Fri>
Number of arrows of object.
Number of ingoing arrows.
SCHT: <2020-05-01 Fri>
Number of outgoinf arrows.
Matrix of connection of odjects {-1,0,1}
.
Allow adding type signatures to type class function instance declaration.
SCHT: <2020-05-01 Fri>
If every vertex in a graph is reachable from every other vertex.
It is possible to find all strongly connected components (and that way also test graph for strong connectivity), in linear time (Θ(V+E)
).
Binary relation of being strongly connected is an equivalence relation.
<<<Strongly-connected>>>
Full strongly connected subgraph of some graph.
* of a directed graph G is a subgraph that is strongly connected, and has property: no additional edges or vertices from G can be included in the subgraph without breaking its property of being strongly connected.
<<<SCC>>> <<<Strongly connected components>>> <<<Strongly-connected component>>> <<<Strongly-connected components>>>
Method of embedding eDSL in a typed functional host language (Haskell). Alternative to the embedding as a (generalized) algebraic data type. For parsers of DLS expressions: (1/partial) evaluator, compiler, pretty printer, multi-pass optimizer.
* embedding is writing denotational semantics for the DSL in the host language.
Approach can be used iff eDSL is typed. Only well-typed terms become embeddable, and host language can implemen also a eDSL type system. Approach that eDSL code interpretations are type-preserving.
One of main pros of * - extensibility: implementation of DSL can be used to analyze/evaluate/transform/pretty-print/compile and interpreters can be extended to more passes, optimizations, and new versions of DSL while keeping/using/reusing the old versions.
Example fields of application: language-integrated queries, non-deterministic & probabilistic programming, delimiter continuation, computability theory, stream processsing, hardware description languages, generation of specialized numerical kernels, semantics of natural language.
Operators then their operands.
<<<Polish notation>>> <<<PN>>>
Operands then their opration.
<<<Reverse Polish notation>>> <<<PRN>>>
“One of the finer points of the Haskell community has been its propensity for recognizing abstract patterns in code which have well-defined, lawful representations in mathematics.” (Chris Allen, Julie Moronuki - “Haskell Programming from First Principles” (2017))
SCHT: <2020-09-18 Fri>
Use data type aliases to deferentiate logic of values.
SCHT: <2021-01-28 Thu>
Wider the type the more it is polymorphic, means it has broader application and fits more types.
The more constrained system has more usefulness.
Unconstrained means most flexible, but also most useless.
SCHT: <2020-10-24 Sat>
print :: Show a => a -> IO ()
print a = putStrLn (show a)
SCHT: <2020-07-09 Thu>
foldr
spine recursion intermediated by the folding. Can terminate at any point.
foldl
spine recursion is unconditional, then folding starts. Unconditionally recurses across the whole spine, if it infinite - infinitely.
SCHT: <2020-09-18 Fri>
Model the domain and types before thinking about how to write computations.
SCHT: <2020-05-18 Mon>
Product types can be tested as a product of random generators.
Sum types require to implement generators with separate constructors, and picking one of them, use oneof
or frequency
to pick generators.
In Haskell inline composition requires:
h.g.f $ i
Function application has a higher priority than composition. That is why parentheses over argument are needed. This precedence allows idiomatically compose partially applied functions.
But it is a way better then:
h (g (f i))
SCHT: <2020-07-21 Tue>
Use Tacit very carefully - it hides types and harder to change code where it is used. Use just enough Tacit to communicate a bit better. Mostly only partial point-free communicates better.
SCHT: <2020-10-07 Wed>
BigData and OLAP analysis.
SCHT: <2020-09-18 Fri>
Function application on n levels beneath:
(fmap . fmap) function twoLevelStructure
How fmap . fmap
typechecks:
(.) :: (b -> c) -> (a -> b) -> a -> c
fmap :: Functor f => (m -> n) -> f m -> f n
fmap :: Functor g => (x -> y) -> g x -> g y
fmap . fmap :: (Functor f, Functor g)
=> ((g x -> g y) -> f . g x -> f . g y)
-> (( x -> y) -> g x -> g y)
-> ( x -> y) -> f . g x -> f . g y
fmap . fmap :: (x -> y) -> f . g x -> f . g y
In functions parameter order is important. It is best to use first the most reusable parameters. And as last one the one that can be the most variable, that is important to chain.
There can be more than one valid Monoid for a data type. && There can be more than one valid Applicative instance for a data type. -> There can be differnt Applicatives with different Monoid implementations.
SCHT: <2020-07-05 Sun>
Where character is not present - discard the according processing of a parameter.
(>> )
is an exception, it does the reverse. ignores the first parameter, in fact >> \equiv *>
.
= *>= does the proper action: does calculation, but ignores the value from the first argument.
SCHT: <2020-08-09 Sun>
Trailing _
means ignoring the result.
{- |
Module : <File name or $Header$ to be replaced automatically>
Description : <optional short text displayed on contents page>
Copyright : (c) <Authors or Affiliations>
License : <license>
Maintainer : <email>
Stability : unstable | experimental | provisional | stable | frozen
Portability : portable | non-portable (<reason>)
<module description starting at first column>
-}
SCHT: <2020-12-24 Thu>
Typed holes help build code in complex situations.
SCHT: <2020-09-28 Mon>
That is why infinite types throw infinite type error.
SCHT: <2020-05-13 Wed>
Even if there is types - define type synonims. They are free. That distinction with synonims, would allow TypeSynonymInstances, which would allow to create a diffrent type class instances and behaviour for different information.
If you wrote code and really needed only those - move that code to Applicative.
return -> pure
ap -> <*>
liftM -> liftA -> <$>
>> -> *>
Can be rewriten in Applicative:
func = do
a <- f
b <- g
pure (a, b)
Can’t be rewritten in Applicative:
somethingdoSomething' n = do
a <- f n
b <- g a
pure (a, b)
(f n) creates monadic structure, binds ot to a wich is consumed then by g.
With Type Applicative every condition fails/succseeds independently. It needs a boilerplate data constructor/value pattern matching code to work. And code you can write only for so many cases and types, so boilerplate can not be so flexible as Monad that allows polymorphism. With Type Monad computation can return value that dependent from the previous computation result. So abort or dependent processing can happen.
Linear types are great to control/minimize resource usage.Many languages and Haskell have it all mixup. Here is table showing what belongs to one or other in standard libraries:
Exception | Prelude.catch, Control.Exception.catch, Control.Exception.try, IOError, Control.Monad.Error |
Error | error, assert, Control.Exception.catch, Debug.Trace.trace |
let ... in ...
is a separate expression. In contrast, where
is bound to a surrounding syntactic construct (namespace).
SCHT: <2020-05-01 Fri>
Can powerfully synergyze with ScopedTypeVariables.
Practice to address orphan instances:
Does type class or type defined by you:
Type class | Type | Recommendation |
---|---|---|
\check | {Type, instance} in the same module | |
\check | {Type class & instance} in the same module | |
{Define newtype wrap, its instances} in the same module |
Only proper smart constructors should be exported. Do not export data type constructor, only a type.
In * all morphisms are epimorphisms and monomorphisms.
Writing/thinking about recursion:
- Find the base cases, om imput of which the answer can be provided right away. There is mosly one base case, but sometimes there can be several of them. Typical base cases are: zero, the empty list, the empty tree, null, etc.
- Do inductive case. The recursive invocation. The argument of a recursive call needs to be smaller then the current argument. So it would be gradually closer to the base case. The idea is that processes eventually hits the base case.
Simple functional application is used in the recursion. Assume that the functions would return the right result.
SCHT: <2020-08-15 Sat>
<>
:
Sets - union.
Maps - left-biased union.
Number - Sum
, Product
form separate monoid categories.
SCHT: <2020-06-14 Sun>
The main case of usage of Free monads in Haskell:
Start implementation of the monad from a Free monad, drafting the base monadic operations, then add custom operations.
Gradually build on top of Free monad and try to find homomorphisms from monad to objects, and if only objects are needed - get rid of the free monad.
head
and tail
and alike functions are often partial (unsafe) funcitons.
Example:
instance (Monad m) => Functor (StateT s m) where
fmap f m = StateT $ \s -> do
(x, s') <- runStateT m s -- Here is a pattern matching bind
return (f x, s')
Giving not Monad
but Applicative
requirement allows parralel computation, but if there should be a chaining of the intemidiate state - it must be monadic.
Reader
trait: (r ->)
.
Writer
trait: (a, w)
.
State
trait is combination of both:
newtype StateT s m a =
StateT { runStateT :: s -> m (a, s) }
newtype ReaderT r m a =
ReaderT { runReaderT :: r -> m a }
newtype WriterT w m a =
WriterT { runWriterT :: m (a, w) }
State
trait fully replaces writer
.
SCHT: <2020-05-01 Fri>
From the lift . pure = pure
follows that MonadTrans
type can have a pure
defined with lift
.
Stacking of MonadTrans
monads can result in a lot of chained lift
and unwraps. There is many ways to cope with that but the most robust and common is to abstract representation with newtype
on the Monad
stack. This can reduce caining or remove the manual lifting withing the Monad.
For perfect combination for contributors to be able to extend the code - keep the Internal
module that has a raw representation.
let
and where
create a recursive set of definitions with can explode, don’t mix them togather in code.
Let is self-recursive lazy pattern. It is checked and errors only at execution time. Binds only inside expression it is binded to.
Where is a part of definition, scoped over definition implemetations and guards, not self-recursive.
5.46 <<<Good: The proper nature algorithm that models behaviour of many objects is computation heavy>>>
God does not care about our mathematical difficulties. He integrates empirically.
One who is found of mathematical meaning loves to apply it. But if we implement the “real” algorithms behind nature processes, we face the need to go through the computations of properties of all particles.
Computation of nature is always a middle way between ideal theory behaviour and computation simplification.
5.47 <<<Good: In Haskell parameters bound by lambda declaration instantiate to only one concrete type>>>
Because of let-bound polymorphism:
This is illegal in Haskell:
foo :: (Int, Char)
foo = (\f -> (f 1, f 'a')) id
Lambda-bound function (i.e., one passed as argument to another function) cannot be instantiated in two different ways, if there is a let-bound polymorphism.
Instances for data type can differentiate by constraints & types of arguments. So instance can preserve type boundary, and data type declaration can stay very polymorphic. If the need to extend the type boundaries arrives - the instances may extend, or new instances are created, while used data type still the same and unchanged.
Default ot mtl
.
Transformers
is Haskell 98, doesn’t have funcitonal dependencies, lacks the monad classes, has manual lift of operations to the composite monad.
MTL
extends trasformers
, providing more instances, features and possibilities, may include alternative packages features as mtl-tf
.
- DatatypeContexts
- OverlappingInstances
- IncoherentInstances
- ImpredicativeTypes
- AllowAmbigiousTypes
- UndecidableInstances - often
enumFromTo
enumFromThenTo
reverse
show :: Show a => a -> String
flip
sequence - Evaluate each monadic action in the structure from left to right, and collect the results.
:sprint - show variables to see what has been evaluated already.
minBound - smaller bound
maxBound - larger bound
cycle :: [a] -> [a] - indefinitely cycle s list
repeat - indefinit lis from value
elemIndex e l - return first index, returns Maybe
fromMaybe (default if Nothing) e ::Maybe a -> a
lookup :: Eq a => a -> [(a, b)] -> Maybe b
compare
div - always makes rounding down, to infinity divMod - returns a tuple containing the result of integral division and modulo
concat - [ [a] ] -> [a]
elem x xs - is element a part of a list
zip :: [a] -> [b] -> [(a, b)] - zips two lists together. Zip stops when one list runs out.
zipWith :: (a -> b -> c) -> [a] -> [b] -> [c] - do the action on corresponding elements of list and store in the new list
intersperse :: a -> [a] -> [a] - gets the value and incerts it between values in array
nub - remove duplicates from the list
ord (Char -> Int)
chr (Int -> Char)
isUpper (Char -> Bool)
toUpper (Char -> Char)
quickCheck :: Testable prop => prop -> IO ()
quickCheck . verbose - run verbose mode
List installed packages:
ghc-pkg list
Upstream doc: https://github.com/cachix/cachix
Upstream doc: https://github.com/infinisil/all-hies/#cached-builds
cachix use all-hies
{ config, pkgs, ... }:
let
all-hies = import (fetchTarball "https://github.com/infinisil/all-hies/tarball/master") {};
in {
environment.systemPackages = with pkgs; [
(all-hies.selection { selector = p: { inherit (p) ghc865 ghc864; }; })
];
}
Insert your GHC versions.
Switch to new configuration:
sudo -i nixos-rebuild switch
nix-env -iA selection --arg selector 'p: { inherit (p) ghc865 ghc864; }' -f 'https://github.com/infinisil/all-hies/tarball/master'
Insert your GHC versions.
dotspacemacs-configuration-layers
'(
auto-completion
(lsp :variables
default-nix-wrapper (lambda (args)
(append
(append (list "nix-shell" "-I" "." "--command" )
(list (mapconcat 'identity args " "))
)
(list (nix-current-sandbox))
)
)
lsp-haskell-process-wrapper-function default-nix-wrapper
)
(haskell :variables
haskell-enable-hindent t
haskell-completion-backend 'lsp
haskell-process-type 'cabal-new-repl
)
)
dotspacemacs-additional-packages '(
direnv
nix-sandbox
)
(defun dotspacemacs/user-config ()
(add-hook 'haskell-mode-hook 'direnv-update-environment) ;; If direnv configured
)
Where:
auto-complettion
configures YASnippet
.
nix-sandbox
(https://github.com/travisbhartwell/nix-emacs) has a great helper functions. Using nix-current-sandbox
function in default-nix-wrapper
that used to properly configure lsp-haskell-process-wrapper-function
.
Configuration of the lsp-haskell-process-wrapper-function default-nix-wrapper
is a key for HIE to work in nix-shell
Inside nix-shell
the haskell-process-type 'cabal-new-repl
is required.
Configuration was reassembled from: https://github.com/emacs-lsp/lsp-haskell/blob/8f2dbb6e827b1adce6360c56f795f29ecff1d7f6/lsp-haskell.el#L57 & its authors config: <a href=”https://github.com/sevanspowell/dotfiles/blob/master@@html:@@.spacemacs”>https://github.com/sevanspowell/dotfiles/blob/master.spacemacs/
Refresh Emasc.
Open system monitor, observe the process of environment establishing, packages loading & compiling.
Now, the powers of the Haskell, Nix & Emacs combined. It’s fully in your hands now. Be cautious - you can change the world.
- If recieving sort-of:
readCreateProcess : cabal-helper-wrapper failure
HIE tries to run cabal
operations like on the non-Nix system. So it is a problem with detection of nix-shell
environment, running inside it.
- If HIE keeps getting ready, failing & restarting - check that the projects
ghc --version
is declared in yourall-hie
NixOS configuration.
Additional to default settings it is useful to use -W
, -Wcompat
. -Wall
is for purists and would raise noise. They can be supplied in CLI as also in .cabal
ghc-option. fr
-W
turns on additional useful warnings:
-Wunused-binds
-Wunused-matches
-Wunused-foralls
-Wunused-imports
-Wincomplete-patterns
-Wdodgy-exports
-Wdodgy-imports
-Wunbanged-strict-patterns
-Wall
turns on all warnings that indicate potentially suspicious code.
-Weverything
turns on all warnings supported by compiler.
-Wcompat
turns on warnings that will be enabled by default in the future GHC releases, allows library authors make the code compatible in advance for future GHC releases.
-Werror
promotes warnings into fatal errors, may be useful for CI runs.
-w
turns off all warnings.
Provides:
- set a breakpoints
- observe step-by-step evaluation
- tracing mode
Breakpoints
:break 2
:show breaks
:delete 0
:continue
Step-by-step
:step main
List information at the breakpoint
:list
What been evaluated already
:sprint name
Commands to run the compile/check loop:
cabal
> 3.0
command:
ghcid --command='cabal v2-repl --repl-options=-fno-code --repl-options=-fno-break-on-exception --repl-options=-fno-break-on-error --repl-options=-v1 --repl-options=-ferror-spans --repl-options=-j'
cabal
< 3.0
command:
ghcid --command='cabal new-repl --ghc-options=-fno-code --ghc-options=-fno-break-on-exception --ghc-options=-fno-break-on-error --ghc-options=-v1 --ghc-options=-ferror-spans --ghc-options=-j'
nix-shell
cabal
> 3.0
command:
nix-shell --command 'ghcid --command="cabal v2-repl --repl-options=-fno-code --repl-options=-fno-break-on-exception --repl-options=-fno-break-on-error --repl-options=-v1 --repl-options=-ferror-spans --repl-options=-j" '
nix-shell
cabal
< 3.0
command:
nix-shell --command 'ghcid --command="cabal new-repl --ghc-options=-fno-code --ghc-options=-fno-break-on-exception --ghc-options=-fno-break-on-error --ghc-options=-v1 --ghc-options=-ferror-spans --ghc-options=-j" '
Run Haskell code without first having to compile them.
Official tool in GHC package.
There is a number of good quality projects that export Cabal/Hackage to other packaging systems, big distribution systems and companies rely on them:
- v1 generation of features used/uses own cabal (now legacy) methods of handling packages.
- v2 generation of features (current) uses Nix-like methods internally to handle packages.
Currently Cabal migrated to use of v2 generation by default.
Useful abilities:
exec
- loads the GHC/GHCI env and launches the passed executable.
haddock
- builds the documentaiton and places it into v1 -> dist
, v2 -> dist-newstyle
directories.
sdist
- run a thorough process, properly follow .cabal
instructions, assemble mentioned files and generate a source distribution file .tar.gz
.
upload
- upload source distribution file to Hackage.
Peter Simmons (peti
) - the main creator maintainer maintainer of the Haskell stack and packages (“package set”) in Nixpkgs. He is the central person that created most of the tooling and automation of importing Haskell into Nixpkgs.
Besides documentation of Nixpkgs manual there is a Nixpkgs Haskell lib.
Created/maintained by peti
.
This tool runs on one compiler version.
Allows to clones info from Hackage and convert it into Nix language.
Is developed/resides/embedded in cabal2nix
project.
Also created and maintained by peti
, he uses it for OpenSUSE.
Translates Cabals project description to a Nix expression.
Automatically translates Cabal/Stack project and dependencies into Nix code. Provides IFD (import from derivation) functions that minimize the amount of Nix code that is needed to be added. So it autogenerates Nix code hald way for your purposes.
Project of IOHK and has an active big respectable team.
In Haskell programming spacemacs/jump-to-definition
is your friend, let yourself - it will guide you.
My (Anton-Latukha’s) Spacemacs configuration for Haskell as at: https://github.com/Anton-Latukha/.spacemacs.d/blob/private/init.el. Look there for a Haskell
keyword, there is layer configuration, and the init boot config inside (defun dotspacemacs/user-config ()
.
Since Open Source projects mostly use free tiers of CIs, and different CIs have different features - there is a constant flux of how to construct the best possible integration pipeline for Haskell projects.
The current state of affairs is best put in this quote:
Quote: 2020-02-29: Gabriel Gonzalez about CIs for Haskell Opens Source projectsProbably the biggest constraint is whether or not CI needs to test Windows or OS X, since build machines for those are harder to come by. We currently use AppVeyor for Windows builds and Travis for OS X builds since they are free. For Linux you can basically use any CI provider, but in this case I pay for a Linode VM which I use to host all Dhall-related infrastructure (i.e. all of the *.dhall-lang.org domains), so I reuse that to host Hydra for Nix-related CI so that I can use more parallelism and more efficient caching to test a wider range of GHC versions on a budget.
For testing OS X and Windows platforms we use stack. The main reason we don’t use Nix for either platform is that Nix only supports building release binaries on Linux (and even then it’s still experimental).
So the basic summary I can give is:
For testing everything other than cross-platform support: Nix + Linux is best in my opinion
… because you get much more control and intelligent build caching, which is usually where most CI solutions fall short
For cross-platform support: stack + whatever CI provider provides free builds for that platform
Also, if you ever can pay for your own NixOS VM and you want to reuse the setup I built, you can find the NixOS configuration for dhall-lang.org here:
9.1.2 Safe-exceptions - safe, simple API equivalent to the underlying implementation in terms of power, encourages best practices minimizing the chances of getting the exception handling wrong.
9.1.3 Enclosed-exceptions - capture exceptions from the enclosed computation, while reacting to asynchronous exceptions aimed at the calling thread.
Builds a shell API and parses tose command line options.
Abilities:
- read & validate the arguments passed in any order to the command;
- handle and report errors;
- generate and have comprehensive docs that help user;
- generate context-sensitive complettions for `bash`, `zsh`, `fish`.
Introduction (what library is for) Data model (diagram) – sometimes seeing at once is better then a thousand words of explanation Shortly describe where is speccing happens & belongs, where is parsing happens & belongs, where one can custom hande parsed data on top of what is provided in lib. So now readers roughly know the data model and what are structural parts and where they are
Settings that configure the builder.
long
---key
short
--k
help
- info that is put into docs. Does not affet the parsing.helpDoc
- same ashelp
, but with Doc type support.metavar
- placeholder for the argument seen in the docs. Does not affect the parsing.value
- value by defaultshowdefault
- in the docshidden
- hide from brief infointernal
- hide from descriptionsstyle
- function to apply to descriptionscommand
- add command as asubparser
option.
sample :: Parser Sometype
sample = subparser $ command "hello" $ info hello $ progDesc "Show greeting"
Compose them with <>
.
Example:
( long "example"
<> short 'e'
<> metavar "ARGUMENT_HERE"
<> value "defaultVal"
<> showdefault
<> help "This would produce --example and -e keys for this parser."
<> "It has defaultVal if key was not used."
<> "And it would show default value in help message")
This monoid (Mod f a
) should be given to according builder that accepts it.
Builders are the primitive atomic parsers of the library.
command argument --option optionArgument
- ~argument
- ReadM a -> Mod ArgumentFields a -> Parser a~ General implemetation that uses given reader to parse direct argument.
- ~strArgument
- IsString s => Mod ArgumentFields s -> Parser s~ To consume a string argument directly.
- ~option
- ReadM a -> Mod OptionFields a -> Parser a~ General implementation. Allows to use the given reader.
- ~flag
- a {default value} -> a {active value} -> Mod FlagFields a {option modifier} -> Parser a~
Irrefutable ⇒ no termination for
some
ormany
, for them use ~flag’~. - ~switch
- Mod FlagFields Bool -> Parser Bool~
Macro for Boolean flag:
switch = flag False True
Irrefutable ⇒ no termination for
some
ormany
, for them use ~flag’~ - ~flag’
- a {active value} -> Mod FlagFields a {option modifier} -> Parser a~
Flag parser without a default value. Has sence in composite parser, or when requiring
--on
OR--off
alternatives. - ~infoOption
- String -> Mod OptionFields (a -> a) -> Parser (a -> a)~ Always stops binary and displays a message.
- ~strOption
- IsString s => Mod OptionFields s -> Parser s~ Taking a String argument.
- ~abortOption
- ParseError -> Mod OptionFields (a -> a) -> Parser (a -> a)~ Always fails immediately.
- ~subparser
- Mod CommandFields a -> Parser a~ Command parser. The command modifier can be used to specify individual commands.
Definitions (if there are needed) How parsers are composed from attributes and builders Examples (if there are needed) Option readers Running a parser
Definitions (if there are needed) Applicative on parsers Examples of the use of parsers in the program and how they tie with surrounding data types Alternative Then mention where and how to customize even over that and example
… Rename “How it works” into “How library internally implemented”
SCHT: <2020-07-06 Mon>
On 1-st compilation - * analyzes the abstract signatures without loading side modules, doing the type check with assumption that modules provide right type signatures, the process does not emitt any binary code and stores the intermediate code in a special form that allows flexibily connect modules provided. Which allows later to compile project with particular instanciations of the modules. Major work of this process being done by internal Cabal * support and * system that modifies the intermediate code to fit the module.
9.10.1 “Ivory” - eDSL, safe systems programming, effectively produce C code
Process of exception handling has:
- raising an exception
- gathering information and handling an exception
- ability to finish important sessions/actions independently of whether exception happened or not. That is why it is called guaranteed finalization of important processes.
Exceptions and their handling are for the boundaries that recieve external things that are not under Haskell control. It is mainly an IO handling. The exception mechanism may be used for internal pure Haskell part - if it grew to complex to sort-out some situation try/catch mechanism can be used, but then avoid use of runtime system exceptions catch and sort programmically and generally avoid it.
Its better to promote exceptions to just checking preconditions.
Wraper with exception handler around function (f
) call means that all untreated exception of function or its subfunctions would be caught by this wrapper into the scope where wrapper was used (one syntactic level above function f
).
\begin{tikzcd}
s \arrow[rd, “Handle/dispatch”’] & & &
& m \arrow[rd, “Eval \ inside”’] & & \
& & … \arrow[rd] & \
& & & h \arrow[lluu, “To \ nearest \ exception \ monad”’, dotted, bend right=49]
\end{tikzcd}
Any monad that short-curcuits after some condition check of first argument - has exception handling potential.
Laziness as exceptions are computations - means that some issues would be skipped al togather, in parts that are/were not used would never throw exceptions, but also just as computations - exceptions would be raised at different times and states during computations.
Exception throw breaks purity, function was called buy returned a result.
Try to raise and resolve all exceptions befor aquiring external IO resources. And release all resources when or before the exeption can happen.
With concurrency thread could be killed by other threads (that is called to raise an asyncronous exception in the thread).
- Choose what exceptions to catch. Selection depends on the type.
- No execution of continuation after throw, only handling.
- Handle {,a}synchronous exceptions.
try*
- allows handle Either returning types, bridges the exception handling and basic Haskell computation.handle*
- describes how to handle exception before the monadic action itself.catch*
- describes how to handle the exception after the monadic action itself.
For asyncronous exceptions there are special function to catch them: catchAsync
and handleAsync
.
catch
and handle
are to catch specific exception type.
catches
, catchesDeep
and catchesAsync
allows to catch matching an elements in the list, and then handle them.
bracket*
- computations to aquire and release resource and computation to run in between.finally
- allows to run declared computations afterward (even if an exception was raised).onException
- run computations only if exception happened.
- [X] Exception must include all context information that may be useful.
- [X] Store information in a form for further probable deeper automatic diagnostic.
- [X] Sensitive data/dummies for it - can be useful during development.
- [X] Sensitive data should be stripped from a program logging & exceptions.
- [X] Exception system should be extendable, data storage & representation should be easily extendable.
- [X] Exception system should allow easy exaustive checking of errors, since the different errors can happen.
- [X] Exception system should be automatically well-documented and transparent.
- [X] Exception system should have controllable breaking changes downstream.
- [X] Exception system should allow complex composite (sets) exceptions.
- [X] Exception system should be lightweight on the type signatures of other functions.
- [X] Exception system should automate the collection of context for a exception.
- [X] Exception system should have properties and according functions for particular types of errors.
String
is simple and convinient to throw exception, but really a mistake because it the most cumbersome choise:
- [X] Any Exception instance can be converted to a
String
with eithershow
ordisplayException.
- [ ] Does not include key debugging information in the error message.
- [ ] Does not allow developer to access/manage the Exception information.
- [ ] Exception messages need to be constructed ahead of time, it can not be internationalized, converted to some data/file format.
- [ ] Exception can have a sensitive information that can be useful for developer during work, but should not be logged/shown to end-user. Stripping it from
Strings
in the changing project is a hard task. - [ ] Impossible to rely on this representation for further/deeper inspection.
- [ ] Impossible to have exhaustive checking - no knowledge no check, no warning if some cases are not handled.
- [X] Able to inspect every possible error case with pattern match.
- [X] Self-documenting. Shows the hierarchical system of all exceptions.
- [X] Transparent. Ability to discern in current situation what exceptions can happen
- [ ] New exception constructor causes breaking change to downstream.
- [ ] Wrongly implies completeness. Untreated Errors can happen, different exception can arrive from the outside code.
Sum type must be separate, and product type structure over it. Separate exception type of
- [X] Writing & seing & working with exactly what will go wrong because there is only one possible error for this type of exception. Pattern match happens only onconditions, constructors that should happen.
- [X] Knowledge what exectly goes wrong allows wide usage of Either.
- [ ] It is hard to handle complex exceptions in the unitary system. Real wrorld can return not a particular case, but a set of cases {object not found, path is unreachable, access is denied}.
- [ ] Type signatures grow, and even can become complex, since every case of exception has its own type.
- [ ] Impure
throw
that users can/should use for your code must account for all your exception types.
Exception type entirely opague and inspectable only by accessor functions.
- [X] Updating the internals without breaking the API
- [X] Semi-automates the context of exception with passing it to accessors.
- [X] Predicates can be applied to more than one constructor. Which are properties that allows to make complex exceptions much easier to handle.
- [ ] Not self-documenting.
- [ ] Possible options by design are hidden from the downstream, documentation must be kept.
- [ ] When you change the exception handling/throwing errors it does not shows to the downstream.
Provide the set of constructors and also a set of predicates and set of accessors. Use pattern synonyms to provide a documented accessor set without exposing internal data type.
The fail method of Monad has been removed in favor of the method of the same name in the MonadFail class.
MonadFail(..) is now exported from the Prelude and Control.Monad modules. The MonadFailDesugaring language extension is now deprecated, as its effects are always enabled.
So instead of:
import Control.Monad.Fail
...
class MonadFail m => MonadFile m
...
-- use error instead of fail
Nothing -> error ("Message " <> show x)
-- if compatibility fith old GHCs needed (ex. library)
#if __GLASGOW_HASKELL__ < 880
import Prelude hiding (fail)
import Control.Monad.Fail
#endif
Exception cause: external or internal.
Exceptions used by runtime system
div 1 0
-- *** Exception: divide by zero
Exceptions used by programmers:
- Language feature
- Programmable (implemented at library level)
- Ignore
- Repeat
- Wait, stop, exit
- Substitute with default
- Throw
- Handle
- Rethrow
- Emergency exit
Exceptions raised as a result of an “external event”, such as signal from another thread.
Are raised by throwTo
. Are by termin and design should not be catched/handled, by default catching/handling functions are not catching them, if someone still wants to catch them - there are special function: catchAsync
.
Further reading: termin and apparatus were introduced by “Asynchronous Exceptions in Haskell” (Simon Marlow, Simon Peyton Jones, Andrew Moran, John Reppy).
(>>=) :: m a -> (a -> m b) -> m b -- λA.E ∨ A - computes and drops if error value happens.
catch :: c a -> (e -> c a) -> c a -- λE.E ∨ A - handles "errors" as "normal" values and stops when an "error" is finally handled.
Very strong Haskell type system makes possible to work with code from the top down, an axiomatic semantics approach, from constraints into types.
- Helps to form the type level code (aka join points of the code).
- Uses the piling up of constraints/types information. At some point pick and satisfy constraints, can be done one at a time.
- Provides hints through type level formulation for term level calculations, does not formulate the term level.
- Tedious method (a lot of boilerplate and rewriting it) but pretty simple and relaxing.
- Set of constraints.
- When it is needed or convenient, single constraint gets a little more realistically concrete/abstracted.
Main type detail annotation thread can happen in main
or special wrapper function, localization is inside functions.
- Rest of constraints set shifts to source type.
3.a. For the class handled or known how to handle - writte a base case instance description.
instance (Monad m) => MonadReader r (ReaderT r m)
3.b. For others write recursive instance descriptions:
All other unsolved constraints move into the source polymorphic variable.
instance (MonadError e m) => MonadError e (ReaderT r m)
instance (MonadState s m) => MonadState s (ReaderT r m)
- Repeat from 1 until considered done.
- Code condensed into terse form.
MonadError
constraints is IOException
, not for the String
. IOException
vs String
.
Reverse pluck MonadReader
constraint with runReader
on the object.
MonadState
- StateT
Different layering of the same monad transformers is functionality is the same, but the form is different. Surrounding handling functions would need to be different.
Text search (case insensitive):
a
map
con map
Type search:
:: a
:: a -> a
Text & type:
- =id
- a -> a=
Scope is Haskell Platform (and Haskell keywords).
All Hackage packages are available to search with:
fold +Data.Map
finds results in theData.Map
modulefile -System
excludes results from modules such asSystem.IO
,System.FilePath.Windows
andDistribution.System
mode +platform
mode +cmdargs
(only)mode +platform +cmdargs
file -base
(Haskell Platform, excluding the “base” package)
ST is like a lexical scope, where all the variables/state disappear when the function returns https://wiki.haskell.ohttps://www.schoolofhaskell.com/school/to-infinity-and-beyond/older-but-still-interesting/deamortized-strg/Monad/ST https://dev.to/jvanbruegge/what-the-heck-is-polymorphism-nmh
<<<ST-Trick>>>
Allows to separate and preserve information about happened, ex. error handling.
<<<Either data type>>>
- Inverse function
- In logic: \( P → Q ⇒ ¬ P → ¬ Q \), & same for category duality.
- For operation: element that allows reversing operation, having an element that with the dual produces the identity element.
- See Inversion.
- Is a permutation where two elements are out of order.
- See Inverse
\( fx → y ˆ ({fx → y})-1 = {1}x \)
* \( \iff \) function is bijective. Otherwise - partial inverse
SCHT: <2020-11-12 Thu>
For \( f: x → y \): \( ∃ g \ : \ g ˆ f = 1x \) - \( g \) is left inverse of \( f \). \( ∃ g \ : \ f ˆ g = 1y \) - \( g \) is right inverse of \( f \).
* when function is now bijective. When bijective see inverse function.
Enables pattern synonym declaration, which always begins with the pattern
word.
Allows to abstract-away the structures of pattern matching.
<<<Pattern synonym>>> <<<Pattern synonyms>>>
Dump desugarer output.
<<<Desugar>>> <<<GHC desugar>>>
\( O(n^3) \) Always finds optimal reduction into <*> for ApplicativeDo do notation.
Taken from: https://ncatlab.org/nlab/show/computational+trinitarianism
Under the statements:
- propositions as types
- programs as proofs
- relation between type theory and category theory
the following notions are equivalent:
== proposition proof (Logic)
== generalized element of an object (Category theory)
== typed program with output (Type theory & Computer science)
<<<Trinitarism>>>
Do not rely on state, try not to change the state. Use it only when it is very necessary.
Concentrate the state in one place.
Defer state to the last step of the program, or to external system.
Total function uses domain fully, but takes only part of the codomain. Function allows to collapse domain values into codomain value. Meaning the function allows to loose the information. So total function is a computation that looses the information or into bigger codomains. That is why the function has a directionality, and inverse total process is partially possible.
Directionality and invertability are terms.
Emptiness.
Can not be grasped, touched.
A logically uninhabited data type.
(Since basis of logic is tautologically True and Void value can not be addressed - there is a logical paradox with the Void).
Is an object includded into the Hask category, since:
:t (id :: Void -> Void)
(id :: Void -> Void) :: Void -> Void
id
for it exists.
Type system corresponds to constructive logic and not to the classical logic. Classical logic answers the question “Is this actually true”. Constuctive (Intuitionistic) logic answers the question “Is this provable”.
Also has functions:
-- Represents logical principle of explosion: from falsehood, anything follows.
absurd :: Void -> a
-- If Functor holds only Void - it holds no values.
vacuous :: Functor f => f Void -> f a
-- If Monad holds only Void - it holds no values.
vacuousM :: Monad m => m Void -> m a
Design pattern: use polymorphic data types and Void to get rid of possibilities when you need to.
<<<Nothing>>>, Haskell expressions can’t return Void.
Also see: Maybe.
Proposition considered True
due to direct evidence of existence through constructive proof using Curry-Howard isomorphism.
* does not include classic logic fundamental axioms of the excluded middle and double negation elimination. Hense * is weaker then classical logic. Classical logic includes *, all theorems of * are also in classical logic.
<<<Constructive logic>>>
SCHT: <2020-05-07 Thu>
If asserted statement contains some error or contradiction - anything can be proven trough it. The more there is an error - the easier logic chain arrives at any target.
Ancient principle of logic. Both in classical & intuitionistic logic.
<<<Ex falso quodlibet>>> <<<Ex falso sequitur quodlibet>>> <<<EFG>>> <<<Ex contradictione quodlibet>>> <<<Ex contradictione sequitur quodlibet>>> <<<ECQ>>> <<<Deductive explosion>>> <<<Pseudo-Scotus>>>
A property of some construction which boils down to (is manifestly equivalent to) the property that an associated object is a universal initial object of some (auxiliary) category.
Allows the embedding of any category into a category of functors (contravariant set-valued functors) defined on that category. It also clarifies how the embedded category, of representable functors and their natural transformations, relates to the other objects in the larger functor category.
The Yoneda lemma suggests that instead of studying the (locally small) category C {\displaystyle {\mathcal {C}}} \mathcal{C} , one should study the category of all functors of C {\displaystyle {\mathcal {C}}} \mathcal{C} into S e t {\displaystyle \mathbf {Set} } \mathbf{Set} (the category of sets with functions as morphisms). S e t {\displaystyle \mathbf {Set} } \mathbf{Set} is a category we think we understand well, and a functor of C {\displaystyle {\mathcal {C}}} \mathcal{C} into S e t {\displaystyle \mathbf {Set} } \mathbf{Set} can be seen as a “representation” of C {\displaystyle {\mathcal {C}}} \mathcal{C} in terms of known structures. The original category C {\displaystyle {\mathcal {C}}} \mathcal{C} is contained in this functor category, but new objects appear in the functor category, which were absent and “hidden” in C {\displaystyle {\mathcal {C}}} \mathcal{C} . Treating these new objects just like the old ones often unifies and simplifies the theory.
Category equipped with tensor product.
<>
wich is a functor for *.
Set category can be monoidal under both product (having terminal object) or coproduct (having initial object) operations, if according operation exist for all objects.
Any one-object category is *.
\( (a, ()) ∼ a \) up to unique isomorphism, which is called Lax monoidal functor.
Product and coproduct are functorial, so, since: Algebraic data type construction can use:
- Type constructor
- Data constructor
- Const functor
- Identity functor
- Product
- Coproduct
Any algebraic data type is functorial.
Maps all objects of source category into one (fixed) object of target category, and all morphisms to identity morphism of that fixed object.
instance Functor (Const c)
where
fmap :: (a -> b) -> Const c a -> Const c b
fmap _ (Const c) = Const c
In Category theory denoted:
Δ
Last type parameter that bears the target type of lifted function (b
) and is a proxy type.
Analogy: the container that allways has an object attached to it, and everything that is put inside - changes the container type accordingly, and dissapears.
(->) a b = a -> b
Functorial in the last argument & called Reader functor.
newtype Reader c a = Reader (c -> a)
fmap = ( . )
fmap :: (a -> b) -> Op c a -> Op c b
(a -> c) -> (b -> c)
\begin{tikzcd}
a \arrow[r] \arrow[rd] & b \arrow[d, dashed]
& c
\end{tikzcd}
\( (a → b)C = (a ← b)C^{op} \)
class Contravariant f
where
contramap :: (b -> a) -> (f a -> f b)
\begin{tikzcd}
a \arrow[r] \arrow[rd] & b \arrow[d, “contravariant”, dashed]
& c
\end{tikzcd}
If arrows does not commute Contravatiant funtor anyway allows to construct transformation between these such arrows to other arrow.
(->) a b
\( Cop × C → C \)
It is called profunctor.
dimap :: (a' -> a) -> (b -> b') -> p a b -> p a' b'
So, profunctor in case of arrow:
\begin{tikzcd}
a \arrow[dd, “h”] & & a’ \arrow[ll, “f”] \arrow[dd, “profunctor”, dashed]
& & \
b \arrow[rr, “g”] & & b’
\end{tikzcd}
dimap :: (a' -> a) -> (b -> b') -> p a b -> p a' b'
dimap :: f g -> (a -> b) -> (a' -> b')
dimap :: f g -> h -> (a' -> b')
dimap = g . h . f
It is contravariant functor in the first argument, and covariant functor in the second argument.
dimap id <==> fmap
(flip dimap) id <==> contramap
Operates under condition that source and target types have same representation. Same representation means they are type aliases, or it the compiler can infer that they have the same representation. Directly shares the values from the source type to the target type. Conversion is free, there is no run-time computations.
The function implementing the transition:
coerce :: Coercible a b => a -> b
Type class implementing the instances for transitions:
class a ~R# b => Coercible (a :: k0) (b :: k0)
When compiler detects types have same structure, type class instances coerse implementation for this pairs of types. This type class does not have regular instances; instead they are created on-the-fly during type-checking. Trying to manually declare an instance of Coercible is an error.
Coercible
\( ∀ \) Universal quantifier - a general property exists. Global solution. \( ∃ \) Existential quantifier - evidence means general property, a local solution.
\( ∀ \) and \( ∃ \) are dualistic. Especially in Haskell universal type inside function structure has existential-like properties and backwards, existential type has universal-like properties inside function implementation.
Haskell RankNTypes option enables:
forall ... =>
- universal
If variable is universally quantified - the consumer of it can choose the type.
Because the consumer chooses the type the variable inside function body is quantified existentially.
=> ... forall
- existential
If variable is existentially quantified - the type of it treated as it is already determined, and consumer can not reify it - consumer must accept and process the full existential type as it is.
Since the consumer is not involved into the choosing of the type - the variable inside function body quantified universally.
Haskell existentials are always result in throwing aways type information.
Gives ability to work with data from at external world that we do not know definite type at compile time.
Some information about existentially quantified type should be preserved to be able to transrofm it.
Existential wrappers make possible from a function to return existentially quantified data. Wrapper allows to avoid unification with outer context and “escape” type variable.
There are three general degrees how much type information for existential to preserve:
- (low) - use existential variable as is, the use in the code would place it’s own constrants (like
[a]
) and so the abilities to do something with that type variables. - (medium) - povide type class constraints.
- (high) - store existential in parameterized GADT, store type information in GADT constructors, do things and and then restore the type information on pattern match on main GADT constructor and get secondary type.
Additional reading: https://markkarpov.com/post/existential-quantification.html
Propagator is a monotone function between join-semilattices.
Where semilattices are amount of information about individual values. As information on input gained - the information on output only grows.
Join-semilattice is a idempotent commutative monoid.
If there is a system of nodes that each are join semilatice, and proparators are transformations that move information betwen them, and so transmit the information to all of them and bring the system into stable state. Number of times propagator with informaiton fired is not important - because it is idempotent. Order of propagators in the network firing is not important - it is commutative.
Under side-condition for termination (provenance) (information fullness/volume, network becoming stationatry or passing some check) - the network terminates and give a deterministic answer.
Provenance - a ad-hoc rules to determine the probability of recieving an close to trueth result from number of different approaches and informaiton sources. Also solves the contradictory data and raises the question of deciding between the contradictory world views: what is the least … to get the most accurate estimates ….
Dependent types are used in teoretically complex code, in 1-2% of it. GADTs are fit 5-10% of the code.
Proving the easy targets & most needed ones allows much assurance and makes testing coverage more sufficcient.
Liquid Haskell are useful and its refinment types. Ideas presentation.
There is relatively rough idea that codata should use laziness and data should use strictness, which is not really true because there is a lot of cases where being lazy on strict data allows to tramendeusly shorten the computation for data.
You want confluence regardless of totality.
Metaprogramming in Haskell is mainly done through Template Haskell wich is too hard and clunky to work with, due to hard syntax structure.
Unproven Collatz conjecture is a classical computation halting problem. (If xi is even => xi+1 = 3xi+1, if odd => xi+1 = xi/2.
Name it pre-x.x.x.x+1
, so determination of real number happens afterwards.
CHANGELOG.md
template:
# Changelog
## [x.x.x.x](https://github.com/<acc>/<proj>/compare/<oldVer>...<newVer>) (<short-ISO-date>)
* Major (breaking):
* ...
* Medium (extending API features)
* ...
* Minor:
* ...
---
`name` uses [PVP Versioning][1].
[1]: https://pvp.haskell.org
set fork 'f'
set ver '..'
git tag -d $ver
git push --delete $fork $ver
https://hackage.haskell.org/packages/candidates/upload
10.33.14 (careful) Be fully ready when you upload package release to Hackage, since upload is idempotant
http://hackage.haskell.org/packages/upload
Hackage packaging have internal specifics and can refulse to build docs, to generate docs locally and upload them:
nix-shell
set -e
dir=$(mktemp -d /tmp/dist-docs.XXXXXX)
trap 'rm -r "$dir"' EXIT
# assumes cabal 2.4 or later
cabal v2-haddock --builddir="$dir" --haddock-for-hackage --enable-doc
# (pasting pass does not work) Enter _by hand_: account, password
cabal upload -d --publish "$dir/*-docs.tar.gz"
bimap :: (a1 -> a2) -> (b1 -> b2) -> f a1 b1 -> f a2 b2
fmap :: (a -> b) -> f a -> f b
fmap :: (a -> b) -> (Id -> Id) -> f a Id -> f b Id
data IO a
Main data type of the program run-time execution (IO).
All actions should be added to Main.main IO ()
to be executed.
type FilePath = String
Contents & Show
are OS dependent, hold enough data to debug.
data Handle
= FileHandle Filepath ... -- for files
| DuplexHandle Filepath ... -- for streams
Handle - a record used by Haskell runtime system to manage I/O external objects.
Essential properties:
- Direction: In (readable), Out (writable) or both.
- Status: open, semi-closed, closed.
A good practice to close handlers with
hClose
, aslo garbage collector at some point most probaly would remove unused handlers. - Seekable:
True | False
. - Buffering type and always a buffer (even if buffer turned off - buffer is
0
). - Position (there are exceptions)
Position in the data object.
stdin
stdout
stdin
For more info - learn this question in POSIX UNIX/Linux.
data IOMode -- manage
= ReadMode -- input
| WriteMode -- output
| AppendMode -- output
| ReadWriteMode -- input/output
Implementations should enforce locking as far as possible.
Haskell uses multiple-reader | single-writer
locking.
If handle is managing:
- output to a file - no new handls can be allocated for that file.
- input from a file - new non-output handls can be created.
withFile :: FilePath -> IOMode -> (Handle -> IO r) -> IO r
Allows to load the file and run code for it.
openFile :: FilePath -> IOMode -> IO Handle
Directionality of these funciton are determined by IOMode.
hClose :: Handle -> IO ()
Close the handle.
readFile :: FilePath -> IO String
writeFile :: FilePath -> String -> IO ()
appendFile :: FilePath -> String -> IO ()
hFileSize :: Handle -> IO Integer
hIsEOF :: Handle -> IO Bool
isEOF :: IO Bool -- works only on stdin
hGetPosn :: Handle -> IO HandlePosn
hSetPosn :: HandlePosn -> IO ()
data BufferMode
= NoBuffering -- buffering is disabled if possible.
| LineBuffering -- line-buffering should be enabled if possible.
| BlockBuffering (Maybe Int)
-- block-buffering should be enabled if possible.
-- Just - the size of the buffer, otherwise implementation-dependent.
Styles of buffers supported:
- Block-buffering: the write happens when buffer oveflows its size.
- Line-buffering: the write happens when “\n” encountered.
- No buffering: everything is passed-through immidiately.
Buffer also gets written when hflush
is used or handle is closed.
One should not flush less frequently then specified. One can flush buffers more frequently.
The default buffering mode is implementation-dependent on the file system object which is attached to that handle. By default, physical files are block-buffered and terminals are line-buffered.
hSetBuffering :: Handle -> BufferMode -> IO ()
hGetBuffering :: Handle -> IO BufferMode
hFlush :: Handle -> IO ()
version :: Version
getBinDir :: IO FilePath
getLibDir :: IO FilePath
getDynLibDir :: IO FilePath
getDataDir :: IO FilePath
getLibexecDir :: IO FilePath
getSysconfDir :: IO FilePath
Cabal automatically generated module.
ghci
would not load the module, since it was not generated, use cabal v2-repl
to load it.
Ways to pass arguments from function to function:
- Eager/inside-out evaluation: most languages use argument transmission “by-value”. At call time argument expression is evaluated and that value is passed into the function. In this case function can bind the value and change it frevolously - that would not create a mutation outside the funciton, since the function recieved the copy of the initial argument value - so funciton can mutate local value, but that would not mutate a value of the external argument.
- Lazy (outside-in) evaluation - passing an argument by-name. Argument expressions don’t evaluate at call time. Immutability allows to share the argument directly into the function. When on execution of the function body a reference to the parameter is encountered - a coresponding expressions begins evaluation, and since all expressions essentially create a pipeline of algorythm and share the names for identities - the backward pipeline pass from the target request to the initial data can be resolved step by step.
<<<Laziness>>>
Intuitively - fmap
with effects.
Traversable represents traversable structures.
class (Functor t, Foldable t) => Traversable t
where
{-# MINIMAL traverse | sequenceA #-}
-- | Map each element of a structure to an action, evaluate these actions
-- from left to right, and collect the results.
traverse :: Applicative f => (a -> f b) -> t a -> f (t b)
traverse f = sequenceA . fmap f
-- | Evaluate each action in the structure from left to right, and
-- collect the results.
sequenceA :: Applicative f => t (f a) -> f (t a)
sequenceA = traverse id
A point in function where argument equals to the result.
\( f(fix) = fix \)
That means no metter how many times it recurses on itself the result is the same constant:
\( f(f(f(…fix… = fix \)
Not all fixed points are attractive.
For function \( f \), attractive fixed point
- is a fixed point \( x_0 \) for \( f \) such that for any value of \( x \) in the domain that is close enough to \( x_0 \), the recursive applition of \( f \) converges to \( x_0 \).
Attractive fixed points are the special case of a wider mathematical concept of attractors.
The fixed point smallest by order.
- There may be no smallest fixed point - that means there is no fixed points at all.
- If any of fixed points exist - there can be the only one least fixed point, so it is always unique.
Fixed-point theorems mostly yield algorithms for the least fixed point. Least fixed points often have desirable properties that other fixed points do not have.
Since Haskell does not allow infinite types, fixed point can not be expressed in the type signature, so the recoed type is used instead. A type is isomorphic to the recursively approaching the attactive fixed point process of the least fixed point
newtype Fix f = Fix { unFix :: f (Fix f) }
You can imagine that a non-recursive function holds values of the previous iteration.
Design on the organization constraints it to effectively produce the software systems that constrained in the same places.
Original wording (1964):
Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.
The software interface structure of a system will reflect the social organizational boundaries that produced it. Ex, if in development there is one person/team/department that is much harder to work/communicate with - with same functions in the software the API would be scarse and the most probably going through the one central point.
And the contrary - the ways of establishing rules and communications in the company - also would be reflected. Even if company has a tree structure - there is always inordinate and internal undercarpet and open games and communication in it, which mens software structure would have difficulties implementing as a tree structure, and branches would get short-curcuited frequently, where is real-life communication channel, turning the software structure from tree into a semilattice, which is much harder to modularise and decouple.
Generalization of algebra, when it is defined on the Category theory.
Transferring algebraic laws into morphisms eliminates quantification of elements from the axioms, and these algebraic laws may then be glued together in terms of a single functor \( F \), the signature.
packagedb/ | project build cabal metadata package database. |
cache/ | build plan package constraints solver artifacts. Hashes of external packages. |
*.hi | interface modules: type information, public exports, symbol table, other internals of compiled modules. |
*.hie | interface extended file: module symbol data. |
*.hspp | preprocessor. |
cabal_macros.h | CPP-accessible preprocessor definitions. |
*.o | Compiled object files per module. |
*.ll | LLVM source file. |
*.bc | LLVM bytecode. |
*.s | Assembly. |
Cabal file generator YAML-format DSL that aims to reduce repetitions.
DHall excels at doing the same.
Well known event in Haskell history: https://github.com/quchen/articles/blob/master/applicative_monad.md.
Math justice was restored with a RETroactive CONtinuity. Invented in computer science term Applicative (lax monoidal functor) become a superclass of Monad.
& that is why:
return = pure
ap = <*>
>> = *>
liftM = liftA = fmap
liftM* = liftA*
Also, a side-kick - Alternative became a superclass of MonadPlus. Hense:
mzero = empty
mplus = (<|>)
Work of unification continues under: https://gitlab.haskell.org/ghc/ghc/wikis/proposal/monad-of-no-return
<<<Applicative-Monad proposal>>> <<<AMP>>>
In 1998 first solid reference standartization of language was created. Main purpose is that implementors can be committed to rely and support Haskell 98 exactly as it is specified.
In 2002 “Haskell 98” had a minor revision. Next Haskell Report is “Haskell 2010”.
- ∀ class constraint (C t1 .. tn): 1.1. type variables have occurances ≤ head 1.2. constructors+variables+repetitions < head 1.3. ¬ type functions (type func application can expand to arbitrary size)
- ∀ functional dependencies, ⟨tvs⟩_left → ⟨tvs⟩_right, of the class, every type variable in S(⟨tvs⟩_right) must appear in S(⟨tvs⟩_left), where S is the substitution mapping each type variable in the class declaration to the corresponding type in the instance head.
11.1.3 “Great moments in Haskell history” (by Type Classes) - History of Haskell
(Gabriel Gonzalez & contributors)
Good per-direction information on state of Haskell ecosystem.
11.2.2 “Haskell performance” tools, processes, comparisons, data, information, guides
(community)
11.2.3 data Haskell - (2017) annotated links to data science & machine learning libraries, overviews and benchmarks of libraries
dataHaskell contributors
- “GHC User’s Guide Documentation” (GHC Team): PDF
- “What I Wish I Knew When Learning Haskell” (Stephen Diehl & contributors): PDF
- “Category Theory for Programmers” (Bartosz Milewski & contributors): PDF
- Nix manual: HTML
- Nixpkgs manual: HTML
- Nixpkgs Haskell lib: source on the GitHub
Version policy and dependency management.
-- Policy: +--------- big breakage of API, big migration
-- | +------- breakage of API
-- | | +----- non-breaking API additions
-- | | | +--- changes that have no API changes
version: 1.2.3.4
<<<PVP>>>
\textgreek{λειτ} <- \textgreek{λαός} Laos the people \textgreek{ουργός} <- \textgreek{ἔργο} ergon work \textgreek{λειτουργία} leitourgia public work
Moral value of people developed from the community to give back, improving the community.
The life is beautiful. For all humans that make the life have more magic.
This study and work would not be possible without the community: tearchers, mathematicians, Haskellers, scientists, creators, contributors. These sides of people are fascinating.
Special accolades for the guys at Serokell. They were the force that got me inspired & gave resources to seriously learn Haskell and create this pocket guide.