Closed andriytk closed 5 years ago
added 1 commit
added 1 commit
added 1 commit
marked as a Work In Progress
added 1 commit
added 1 commit
changed this line in version 22 of the diff
resolved all discussions
added 1 commit
Suggestion: add a comment above this line, giving a short explanation (not needed to repeat full commit msg though).
added 5 commits
enabled an automatic merge when the pipeline for 12d3fee5ca56dee8487bae433045cfc5d5633672 succeeds
added 6 commits
master
unmarked as a Work In Progress
added 8 commits
master
resolved all discussions
Rebased.
added 17 commits
master
@andriy.tkachuk I propose to rebase this branch onto master after #1538 is landed.
added 3 commits
added 3 commits
added 1 commit
added 1 commit
added 1 commit
marked as a Work In Progress from 05fbb06ea7e501055dac9b6ff23d08f96213355e
added 1 commit
added 1 commit
added 1 commit
added 2 commits
changed the description
unmarked as a Work In Progress
resolved all discussions
added 4 commits
Fixed.
changed this line in version 6 of the diff
added 1 commit
added 1 commit
Well, it might be also a kind of specification by which one could easily determine with which package versions we are supposed to work. Speaking of which, the lower range should be updated as well everywhere probably...
OK. Thanks.
see the history of versions halon was compiled with
git log -p -- stack.yaml
would provide less convoluted way to do that.
I'd prefer to follow the pattern for now.
Which pattern? Do you see any principle of version constraints specifications?
By having this range of version we at least can see the history of versions halon was compiled with. Maybe there is some other reason, like more control over the versions, don't know. But I'd prefer to follow the pattern for now.
There are not so much of them to bother.
It helps to avoid confusion with data type `a'.
marked as a Work In Progress from ad1bc818a1d1153d13c6943588982953f66f1af8
added 3 commits
master
changed this line in version 3 of the diff
changed this line in version 3 of the diff
changed this line in version 3 of the diff
Well, it won't compile with ghc-8.2 without it. If you are asking about ghc-heap-view - some debugging tool? I think we use it when printing some status on halond exit.
lts-11 + ghc-8.2 might allow us to build Halon on arm64!
Note: the stack supports arm64 since 1.7.1 version and starting with ghc-8.2.2.