#12105: merge MatchFixity and HsMatchContext
-------------------------------------+-------------------------------------
Reporter: alanz | Owner: alanz
Type: task | Status: new
Priority: normal | Milestone: 8.2.1
Component: Compiler | Version: 8.0.1
Keywords: | Operating System: Unknown/Multiple
Architecture: | Type of failure: None/Unknown
Unknown/Multiple |
Test Case: | Blocked By:
Blocking: | Related Tickets:
Differential Rev(s): | Wiki Page:
-------------------------------------+-------------------------------------
`MatchFixity` was introduced to facilitate use of API Annotations.
`HsMatchContext` does the same thing with more detail, but is chased
through all over the place to provide context when processing a `Match`.
Since we already have `MatchFixity` in the AST, it may as well provide the
full context.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/12105>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
#12157: Warning priorities (or: report hole warnings first)
-------------------------------------+-------------------------------------
Reporter: ertes | Owner:
Type: feature | Status: new
request |
Priority: normal | Milestone:
Component: Compiler | Version: 8.0.1
Keywords: | Operating System: Unknown/Multiple
Architecture: | Type of failure: None/Unknown
Unknown/Multiple |
Test Case: | Blocked By:
Blocking: | Related Tickets:
Differential Rev(s): | Wiki Page:
-------------------------------------+-------------------------------------
In a typical development workflow some warnings are more useful/urgent
/short-term than others:
{{{#!hs
{-# OPTIONS_GHC -W -fdefer-typed-holes #-}
myFunction x y =
x + _someFunc x + _
}}}
In this example there are three warnings: two holes and one unused
variable. Currently they are reported in the order they come up, which is
usually not a very useful ordering.
One would not want to disable any of them, but with editor integration in
mind it would be very useful to move certain warnings to the top of the
output, so that one does not have to skip countless "unused import" and
"defined, but not used" warnings to finally reach the one hole warning one
actually cares about.
As a quick fix, an option to move hole warnings to the top of the output
would already be of great help. More generally I'd like to ask for a
priority system for different warning types, ideally with sensible
defaults.
Regarding typed holes in particular it would also be useful to be able to
annotate some holes as particularly interesting (short-term vs. long-term
holes), so they appear first among the other hole warnings. It would
suffice to report `_` holes first, then perhaps the single-letter holes
and finally the rest. In the example above, that would mean that the `_`
hole is reported ''before'' the `_someFunc` hole.
Of course all of this also applies to errors. "Not in scope" errors are
usually easy to get out of the way, so some developers may prefer to deal
with them first, while others may prefer to deal with more interesting
errors (like type errors) first.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/12157>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
#4012: Compilation results are not deterministic
-------------------------------------+-------------------------------------
Reporter: kili | Owner: niteria
Type: bug | Status: new
Priority: high | Milestone: 8.2.1
Component: Compiler | Version: 6.12.2
Resolution: | Keywords:
Operating System: Unknown/Multiple | Architecture:
| Unknown/Multiple
Type of failure: Other | Test Case:
Blocked By: 11362 | Blocking:
Related Tickets: #10424 | Differential Rev(s): Phab:D910,
| Phab:D1073, Phab:D1133, Phab:D1192,
| Phab:D1268, Phab:D1360, Phab:D1373,
Wiki Page: | Phab:D1396, Phab:D1457, Phab:D1468,
DeterministicBuilds | Phab:D1487, Phab:D1504, Phab:D1508
-------------------------------------+-------------------------------------
Comment (by Bartosz Nitka <niteria@…>):
In [changeset:"1937ef1c506b538f0f93cd290fa4a42fc85ab769/ghc" 1937ef1/ghc]:
{{{
#!CommitTicketReference repository="ghc"
revision="1937ef1c506b538f0f93cd290fa4a42fc85ab769"
Make UnitIdMap a deterministic map
This impacts at least the order in which version macros are
generated. It's pretty hard to track what kind of nondeterminism
is benign and this should have no performance impact as the number
of packages should be relatively small.
Test Plan: ./validate
Reviewers: simonmar, austin, bgamari, ezyang
Reviewed By: ezyang
Subscribers: thomie
Differential Revision: https://phabricator.haskell.org/D2308
GHC Trac Issues: #4012
}}}
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/4012#comment:191>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
#4012: Compilation results are not deterministic
-------------------------------------+-------------------------------------
Reporter: kili | Owner: niteria
Type: bug | Status: new
Priority: high | Milestone: 8.2.1
Component: Compiler | Version: 6.12.2
Resolution: | Keywords:
Operating System: Unknown/Multiple | Architecture:
| Unknown/Multiple
Type of failure: Other | Test Case:
Blocked By: 11362 | Blocking:
Related Tickets: #10424 | Differential Rev(s): Phab:D910,
| Phab:D1073, Phab:D1133, Phab:D1192,
| Phab:D1268, Phab:D1360, Phab:D1373,
Wiki Page: | Phab:D1396, Phab:D1457, Phab:D1468,
DeterministicBuilds | Phab:D1487, Phab:D1504, Phab:D1508
-------------------------------------+-------------------------------------
Comment (by Bartosz Nitka <niteria@…>):
In [changeset:"3e7a876a9cdf10e5153421b4905928b9de981778/ghc"
3e7a876a/ghc]:
{{{
#!CommitTicketReference repository="ghc"
revision="3e7a876a9cdf10e5153421b4905928b9de981778"
Kill foldUniqSet
I planned to just say that we don't care about this part.
Turns out I was able to document away the uses in the codegenerator.
Test Plan: ./validate
Reviewers: simonmar, austin, bgamari
Subscribers: thomie
Differential Revision: https://phabricator.haskell.org/D2307
GHC Trac Issues: #4012
}}}
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/4012#comment:190>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
