Re: Type-level error messages

2015-10-29 Thread Adam Sandberg Eriksson
When you pulled the latest version from git did you pull both arcanist and libphutil? I think I saw a similar error when I missed one. Also `arc upgrade` should do the right thing for you (in the future). ~adam On Thu, 29 Oct 2015, at 09:23 PM, Iavor Diatchki wrote: > Hello, > > I've updated the

Re: Type-level error messages

2015-10-29 Thread Iavor Diatchki
Hello, I've updated the implementation to match the discussion from this morning. The idea is that `TypeError msd` is a type-family that can never be reduced, similar to `Any`. We don't do anything special in the constraint solver, however when printing errors, if we encounter any constraints of

Re: Type-level error messages

2015-10-28 Thread Iavor Diatchki
I have also written my thoughts on the questions posed by Richard on the wiki page. On Wed, Oct 28, 2015 at 7:07 AM, Richard Eisenberg wrote: > > On Oct 28, 2015, at 10:02 AM, "Augustsson, Lennart" < > lennart.augusts...@sc.com> wrote: > > > I've put in my answers to your questions. > > And I

Re: Type-level error messages

2015-10-28 Thread Richard Eisenberg
On Oct 28, 2015, at 10:02 AM, "Augustsson, Lennart" wrote: > I've put in my answers to your questions. And I've responded. ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Type-level error messages

2015-10-28 Thread Richard Eisenberg
On Oct 28, 2015, at 7:39 AM, Ben Gamari wrote: > It does look pretty reasonable but keep in mind that there are a number > of comments on the Phabricator Diff that still need to be addressed. And I have three burning questions at the bottom of the wiki page https://ghc.haskell.org/trac/ghc/wik

Re: Type-level error messages

2015-10-28 Thread Ben Gamari
Iavor Diatchki writes: >> I think that the branch should be in an OK state, except that it is not >> merged with the latest HEAD. > It does look pretty reasonable but keep in mind that there are a number of comments on the Phabricator Diff that still need to be addressed. Thanks! - Ben signa

RE: Type-level error messages

2015-10-27 Thread Simon Peyton Jones
It would be great to document some of these common workflows. Simon | -Original Message- | From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Matthew | Pickering | Sent: 27 October 2015 21:10 | To: Iavor Diatchki | Cc: ghc-devs@haskell.org | Subject: Re: Type-level error

Re: Type-level error messages

2015-10-27 Thread Matthew Pickering
t;> > Hello, >> > >> Hello! >> >> Very good timing on the message; we just finished discussing your work >> not more than an hour ago. You can disregard my message; I didn't notice >> yours before sending it. >> >> > On Thu, Oct 22, 2015 at 9:

Re: Type-level error messages

2015-10-27 Thread Iavor Diatchki
eyton Jones < > simo...@microsoft.com> > > wrote: > > > >> I’ve forgotten the state of your type-level error messages work. How’s > it > >> going? > >> > >> I think we should try to add it to 8.0.1. The current status is that > the

Re: Type-level error messages

2015-10-27 Thread Ben Gamari
t; >> I’ve forgotten the state of your type-level error messages work. How’s it >> going? >> >> I think we should try to add it to 8.0.1. The current status is that the >> idea is implemented on a branch. Then, there were some comments and >> sugge

RE: Type-level error messages

2015-10-27 Thread Ben Gamari
Simon Peyton Jones writes: > I’ve forgotten the state of your type-level error messages work. How’s it > going? > > Iavor Diatchki writes: > > > I think we should try to add it to 8.0.1. The current status is that > > the idea is implemented on a branch. The

Re: Type-level error messages

2015-10-27 Thread Iavor Diatchki
Hello, On Thu, Oct 22, 2015 at 9:47 AM, Simon Peyton Jones wrote: > I’ve forgotten the state of your type-level error messages work. How’s it > going? > > I think we should try to add it to 8.0.1. The current status is that the > idea is implemented on a branch. Then,

RE: Type-level error messages

2015-10-22 Thread Simon Peyton Jones
I’ve forgotten the state of your type-level error messages work. How’s it going? I think we should try to add it to 8.0.1. The current status is that the idea is implemented on a branch. Then, there were some comments and suggestions that maybe we should do things in a different way