- User Since
- Dec 18 2014, 1:25 PM (118 w, 3 d)
Fri, Mar 24
Yes, this is a good idea but the implementation of the function could be improved.
Thu, Mar 23
- updated comments
Tue, Mar 21
Ok the code looks good now but still some error message wibbles I think.
Mon, Mar 20
Perhaps it is because you are forcing instances to be loaded which are not imported by them module you are testing.
Try changing the error message to print out all possible instances and then seeing which ones are different before and after your patch.
Sun, Mar 19
It seems the error messages now contain redundant information when a binding is both "relevant" and "very relevant" (type correct).
Fri, Mar 17
The paper this links to is not finished but at least the first half is fairly complete and explains the purpose of the strictness analyser.
Thu, Mar 16
Tue, Mar 14
Is this actually faster given the cost of constructing a set each time? I don't have good intuition for this but I have thought about doing it before.
Sun, Mar 12
Not the right place. The stderr output of ./validate is quite different on my machine to harbormaster which makes this difficult to debug.
Sat, Mar 11
Wed, Mar 8
What are these tests meant to test? Why does qq006 depend on parsec, that doesn't seem very robust.
Mon, Mar 6
Fri, Mar 3
Wed, Mar 1
Gipeda graph which will hopefully catch up to this point - https://perf.haskell.org/ghc/#graph/tests/alloc/T12234;hl=55efc9718b520ef354e32c15c4b49cdfecce412f
Sun, Feb 26
It also appears the repository was set incorrectly. Using arc diff is much easier in my experience!
Did you create this using the web interface? It is much better if you can create the diff using arc so that CI runs.
@Nolan You can update revision by using arc diff --update D3212 in future to avoid having to create a new differential.
Sat, Feb 25
Adding Reid who has previously expressed an opinion about the amount of compiler output.
The build log js around 1200 lines after this change.
Put the flag in the right place..
Fri, Feb 24
- Fix build
Feb 24 2017
Feb 22 2017
@austin tells me that this should now be fixed.
Feb 21 2017
Yes you are right.
It is really hard to see what is going on here. Perhaps you could put each commit up as a separate diff?
Feb 19 2017
Feb 18 2017
Feb 17 2017
Feb 16 2017
Does your patch actually compile? arc is working again now, please can you update the diff so I can see it more clearly?
Feb 15 2017
I don't think a test is necessary.
Feb 14 2017
Feb 13 2017
This commit seems like it broke the OS X build.
Feb 12 2017
Feb 10 2017
This passes for me now on OS X.
Like I said on the commit. The test also fails on OS X due to differences between clang and gcc I guess. I can try to test this locally so you are not waiting years for the builder to finish.
Also failing on OS X
Feb 9 2017
What command were you running?
Feb 7 2017
This isn't the right fix it seems.
Feb 6 2017
Also the differential description needs to be updated to describe the feature as this will become the commit message.
@amindfv Please can you upload you SSH key and update the diff (using arc diff --update D2822) so that the changes are pushed to the staging repo and built by harbormaster?
Feb 4 2017
- Simon's comments and update existing test to test strictness properties
I don't really think the pattern match checker is the right place to issue an inaccessibility warning so I think this is done for now.
- Choose right base commit
- Update with new base commit
- Accept new test output
Good job you spotted this Reid.