- ghc-tickets - Haskell.org

[GHC] #10222: Data.Foldable should have genericLength
by GHC 31 Mar '15

31 Mar '15

#10222: Data.Foldable should have genericLength -------------------------------------+------------------------------------- Reporter: uznx | Owner: Type: feature | Status: new request | Milestone: Priority: normal | Version: 7.10.1 Component: | Operating System: Unknown/Multiple libraries/base | Type of failure: None/Unknown Keywords: | Blocked By: Architecture: | Related Tickets: Unknown/Multiple | Test Case: | Blocking: | Differential Revisions: | -------------------------------------+------------------------------------- The "length" function in Data.Foldable has its return type hardcoded to "Int". There should also be a genericLength function which can return any Num type, similar to Data.List.genericLength. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10222> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 1

Re: [GHC] #3699: Wildcards in type functions
by GHC 31 Mar '15

31 Mar '15

#3699: Wildcards in type functions -------------------------------------+------------------------------------- Reporter: | Owner: MartijnVanSteenbergen | Status: new Type: feature request | Milestone: 7.12.1 Priority: low | Version: 6.10.4 Component: Compiler (Type | Keywords: newcomer checker) | Architecture: Resolution: | Unknown/Multiple Operating System: Unknown/Multiple | Test Case: Type of failure: None/Unknown | Blocking: Blocked By: | Differential Revisions: Related Tickets: | -------------------------------------+------------------------------------- Comment (by dalaing): I thought about this a little last night and realised that the resolution should be the same as for unused type variables. Your comment confirms that and gives a few hints on where to get started - so thanks heaps! -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/3699#comment:16> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

Re: [GHC] #4806: Make error message more user friendly when module is not found because package is unusable
by GHC 30 Mar '15

30 Mar '15

#4806: Make error message more user friendly when module is not found because package is unusable -------------------------------------+------------------------------------- Reporter: mitar | Owner: Type: feature request | Status: infoneeded Priority: low | Milestone: 7.12.1 Component: Compiler | Version: 7.0.1 Resolution: | Keywords: newcomer Operating System: Unknown/Multiple | Architecture: Type of failure: None/Unknown | Unknown/Multiple Blocked By: | Test Case: Related Tickets: | Blocking: | Differential Revisions: -------------------------------------+------------------------------------- Changes (by thomie): * keywords: => newcomer -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/4806#comment:8> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

Re: [GHC] #4931: hsc2hs emits invalid OPTIONS_GHC pragmas
by GHC 30 Mar '15

30 Mar '15

#4931: hsc2hs emits invalid OPTIONS_GHC pragmas -------------------------------------+------------------------------------- Reporter: awson | Owner: Type: bug | Status: new Priority: low | Milestone: 7.12.1 Component: hsc2hs | Version: 7.0.1 Resolution: | Keywords: newcomer Operating System: Unknown/Multiple | Architecture: Type of failure: None/Unknown | Unknown/Multiple Blocked By: | Test Case: Related Tickets: | Blocking: | Differential Revisions: -------------------------------------+------------------------------------- Changes (by thomie): * keywords: => newcomer Comment: See comment:5. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/4931#comment:7> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

Re: [GHC] #3699: Wildcards in type functions
by GHC 30 Mar '15

30 Mar '15

#3699: Wildcards in type functions -------------------------------------+------------------------------------- Reporter: | Owner: MartijnVanSteenbergen | Status: new Type: feature request | Milestone: 7.12.1 Priority: low | Version: 6.10.4 Component: Compiler (Type | Keywords: newcomer checker) | Architecture: Resolution: | Unknown/Multiple Operating System: Unknown/Multiple | Test Case: Type of failure: None/Unknown | Blocking: Blocked By: | Differential Revisions: Related Tickets: | -------------------------------------+------------------------------------- Comment (by jstolarek): I always imagined that `_` will be instantiated internally to a fresh type variable. This means that this feature would mostly affect the parser and renamer and by the time you reach the point when your example collision is checked (`FamInst.checkForConflicts`, called from `FamInst.checkFamInstConsistency`) the example code will look like: {{{#!hs type instance Testing (f :>: a_1234) = MyType f type instance Testing (a_5678 :>: g) = MyType g }}} where `a_1234` and `a_5678` are fresh type variables. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/3699#comment:15> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

Re: [GHC] #3699: Wildcards in type functions
by GHC 30 Mar '15

30 Mar '15

#3699: Wildcards in type functions -------------------------------------+------------------------------------- Reporter: | Owner: MartijnVanSteenbergen | Status: new Type: feature request | Milestone: 7.12.1 Priority: low | Version: 6.10.4 Component: Compiler (Type | Keywords: newcomer checker) | Architecture: Resolution: | Unknown/Multiple Operating System: Unknown/Multiple | Test Case: Type of failure: None/Unknown | Blocking: Blocked By: | Differential Revisions: Related Tickets: | -------------------------------------+------------------------------------- Comment (by dalaing): How would we resolve things like {{{#!hs type instance Testing (f :>: _) = MyType f type instance Testing (_ :>: g) = MyType g }}} and other such collisions? I'm pretty new to GHC - is there an existing resolution order from elsewhere that could be borrowed for this? -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/3699#comment:14> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

[GHC] #10212: The testsuite cleans up hpc files, even if they are part of a test.
by GHC 30 Mar '15

30 Mar '15

#10212: The testsuite cleans up hpc files, even if they are part of a test. -------------------------------------+------------------------------------- Reporter: dalaing | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Test Suite | Version: 7.11 Keywords: | Operating System: Unknown/Multiple Architecture: | Type of failure: None/Unknown Unknown/Multiple | Blocked By: Test Case: hpc/T10138 | Related Tickets: Blocking: | Differential Revisions: | -------------------------------------+------------------------------------- Multiple validate runs start to fail hpc/T10138, since the .tix file and .hpc directory get cleaned up. It seems there are two options here - we could make the test generate the .tix file and .hpc directory as it runs, or we could add an option to the test driver to not clean those files up for certain tests. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10212> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 6

[GHC] #9933: Cross-compile failure : Not in scope: ‘gcdInt'’
by GHC 30 Mar '15

30 Mar '15

#9933: Cross-compile failure : Not in scope: ‘gcdInt'’ -------------------------------------+------------------------------------- Reporter: erikd | Owner: erikd Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.11 Keywords: | Operating System: Architecture: Unknown/Multiple | Unknown/Multiple Difficulty: Unknown | Type of failure: Building Blocked By: | GHC failed Related Tickets: | Test Case: | Blocking: | Differential Revisions: -------------------------------------+------------------------------------- When cross-compiling from x86_64-linux to armhf-linux using the `quick- cross` setting from `mk/build.mk.sample` I get: {{{ libraries/base/GHC/Real.hs:28:25: Not in scope: ‘gcdInt'’ libraries/base/GHC/Real.hs:28:34: Not in scope: ‘gcdWord'’ }}} It turns out these functions are exported un-conditionally but are only defined within an `#ifdef`. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/9933> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 2

Re: [GHC] #2168: ghci should show haddock comments for identifier
by GHC 29 Mar '15

29 Mar '15

#2168: ghci should show haddock comments for identifier -------------------------------------+------------------------------------- Reporter: j.waldmann | Owner: Type: feature request | Status: new Priority: normal | Milestone: 7.12.1 Component: GHCi | Version: 6.8.2 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: None/Unknown | Unknown/Multiple Blocked By: | Test Case: Related Tickets: | Blocking: | Differential Revisions: -------------------------------------+------------------------------------- Changes (by hvr): * cc: Fuuzetsu (added) * priority: lowest => normal Comment: Adding Mateusz who may be able to contribute some comments, as I've been bugging him for some time already about adding the raw Haddock markup to `.hi` files... :-) -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/2168#comment:21> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

Re: [GHC] #2168: ghci should show haddock comments for identifier
by GHC 29 Mar '15

29 Mar '15

#2168: ghci should show haddock comments for identifier -------------------------------------+------------------------------------- Reporter: j.waldmann | Owner: Type: feature request | Status: new Priority: lowest | Milestone: 7.12.1 Component: GHCi | Version: 6.8.2 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: None/Unknown | Unknown/Multiple Blocked By: | Test Case: Related Tickets: | Blocking: | Differential Revisions: -------------------------------------+------------------------------------- Changes (by waern): * cc: hvr (added) * failure: => None/Unknown Comment: Like Igloo said, I think we should just add Haddock comments to the .hi files. We are already storing meta data in there such as annotations. Incidentally, if we do this then Haddock might also eventually be able to generate docs purely based on .hi files (useful in some cases). -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/2168#comment:20> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0