Giter VIP home page Giter VIP logo

haskell-exercises's People

Contributors

elliotdavies avatar jordymoos avatar jwhiles avatar minimumviableperson avatar moleike avatar qrilka avatar zooeymiller avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

haskell-exercises's Issues

KindSignatures: it would be helpful to talk about kind inference through method signatures

@i-am-tom I am going through the haskell exercises, and in the KindSignatures section I noticed that you explain how class Something a will have a kind of *, and you can change that by adding the KindSignatures pragma.

I think this is great, but I feel there’s a step in between that could be explained to avoid confusion. That is, GHC will correctly infer the type of a based on the method signatures provided, and most of the time you will provide method signatures, so you might not need to jump straight into KindSignatures for it.

class Functor f where
  fmap :: (a -> b) -> f a -> f b

:k Functor
Functor :: (* -> *) -> Constraint


class Stuff a where
   lol :: a b c d

:k Stuff
Stuff :: (* -> * -> * -> *) -> Constraint

This also explains why you mention that it’s a good pragma to make documentation more explicit.

MultiParamTypeClasses explanation

A few notes on the MPTC explanation while I remember:

Solutions?

Thank you so much for the course!
Is there any link to the canonical solutions?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.