<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">Il giorno 30/mar/2015, alle ore 19:17, Oliver Charles <<a href="mailto:ollie@ocharles.org.uk" class="">ollie@ocharles.org.uk</a>> ha scritto:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">You're in the right ballpark that's for sure - and your experience with hard-to-decode error messages is not a new one either! Haskell is somewhat "experiemental" in this domain, as its only now starting to learn the features necessary to do what you want to do.<div class=""><br class=""></div></div></div></blockquote><div><br class=""></div><div>Having some compilers background I understand very well the difficulties in making sensible error messages,</div><div>especially when dealing with such advanced features. The point was more that I don’t know the basics on</div><div>how those features work (and what is involved in the job of the type checker) so I can’t even parse what </div><div>GHC try to tell me (skolem what?).</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">I think some of the best work to learn the latest techniques is described here: <a href="https://github.com/jstolarek/dep-typed-wbl-heaps-hs" class="">https://github.com/jstolarek/dep-typed-wbl-heaps-hs</a></div><div class=""><br class=""></div></div></div></blockquote><div>Thank you that looks very useful!</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">-- ocharles</div></div></div></blockquote></div><br class=""><div class="">Greetings,</div><div class="">Nicola</div></body></html>