You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 18, 2026. It is now read-only.
tl;dr: Mention that :t output will not be useful until 102 material.
This is something we have discussed a few times in the past.
Until typeclasses in 102, types even for simple functions such as (+) and div are not really that helpful.
We have tried looking into monomorphising ghci output and considered writing a replacement for a limited number of operations in Prelude, so that during 101 people would not see typeclasess.
While been technically challenging, it might also not be the best solution from the educational standpoint.
An alternative is to mention, in 101, that types people will see when they type :t involve abstractions covered in 102, and just suggest they wait until 102, to understand them.
We literally start 102 with slides that explain what those types are.
tl;dr: Mention that
:toutput will not be useful until 102 material.This is something we have discussed a few times in the past.
Until typeclasses in 102, types even for simple functions such as
(+)anddivare not really that helpful.We have tried looking into monomorphising ghci output and considered writing a replacement for a limited number of operations in Prelude, so that during 101 people would not see typeclasess.
While been technically challenging, it might also not be the best solution from the educational standpoint.
An alternative is to mention, in 101, that types people will see when they type
:tinvolve abstractions covered in 102, and just suggest they wait until 102, to understand them.We literally start 102 with slides that explain what those types are.