- ghc-tickets - Haskell.org

[GHC] #8556: Invalid constructor names are accepted in data declarations
by GHC 23 Mar '15

23 Mar '15

#8556: Invalid constructor names are accepted in data declarations ------------------------------------+------------------------------------- Reporter: dolio | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.6.3 Keywords: | Operating System: Unknown/Multiple Architecture: Unknown/Multiple | Type of failure: None/Unknown Difficulty: Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | ------------------------------------+------------------------------------- Earlier today, someone was asking on #haskell why the constructor name {{{(^)}}} wouldn't work in GADT definitions. My response was that {{{(^)}}} isn't a constructor name, but much to my surprise, GHC accepts such names in a regular data declaration: {{{ data Foo = F | (^^^^) Int Int }}} This creates a {{{Foo}}} type and value constructor {{{F}}}, but no value constructor {{{(^^^^)}}}. However, in 7.6.3, if DataKinds are enabled, both constructors appear at the type level. In HEAD, the same definition is accepted, with only {{{F}}} existing at the value level, as before. But at the type level, both {{{F}}} and {{{(^^^^)}}} just generate errors that {{{Foo}}} is not a promotable type. At that point, I think there's no question that the declaration should just be ruled out. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8556> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 3

[GHC] #10179: Kinds missing from types in ghci
by GHC 23 Mar '15

23 Mar '15

#10179: Kinds missing from types in ghci -------------------------------------+------------------------------------- Reporter: br1 | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: GHCi | Version: 7.10.1-rc2 Keywords: | Operating System: Unknown/Multiple Architecture: | Type of failure: None/Unknown Unknown/Multiple | Blocked By: Test Case: | Related Tickets: Blocking: | Differential Revisions: | -------------------------------------+------------------------------------- {-# LANGUAGE TypeFamilies #-} {-# LANGUAGE DataKinds #-} {-# LANGUAGE PolyKinds #-} data family F (a:: k) foo :: F (m :: [()]) -> a foo = undefined bar :: F (m :: [[()]]) -> a bar = undefined according to GHCi, both foo and bar have type F m -> a but [foo, bar] fails -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10179> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 3

[GHC] #9194: Remove magic parsing of (~)
by GHC 23 Mar '15

23 Mar '15

#9194: Remove magic parsing of (~) ------------------------------------+------------------------------------- Reporter: goldfire | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.8.2 Keywords: | Operating System: Unknown/Multiple Architecture: Unknown/Multiple | Type of failure: None/Unknown Difficulty: Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | ------------------------------------+------------------------------------- It seems that `(~)` has magical parsing: {{{ Prelude> :i (~) <interactive>:1:2: parse error on input ‘~’ Prelude> :k (~) (~) :: k -> k -> Constraint Prelude> :i (+) -- for comparison class Num a where (+) :: a -> a -> a ... -- Defined in ‘GHC.Num’ infixl 6 + }}} Now that type operators do not need to start with a colon, this magic seems unnecessary. The `(~)` syntax does not need to be wired-in, unless I'm missing something. (The ''definition'' of `(~)` needs to be wired in -- it's just the syntax that doesn't need to be.) -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/9194> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 5

Re: [GHC] #4243: Make a proper options parser for the RTS
by GHC 23 Mar '15

23 Mar '15

#4243: Make a proper options parser for the RTS -------------------------------------+------------------------------------- Reporter: igloo | Owner: carlostome Type: task | Status: new Priority: normal | Milestone: 7.12.1 Component: Runtime System | Version: 6.13 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: None/Unknown | Unknown/Multiple Blocked By: | Test Case: Related Tickets: #9839 | Blocking: 7535 | Differential Revisions: -------------------------------------+------------------------------------- Changes (by carlostome): * owner: => carlostome -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/4243#comment:14> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

Re: [GHC] #4150: CPP+QuasiQuotes confuses compilation errors' line numbers
by GHC 23 Mar '15

23 Mar '15

#4150: CPP+QuasiQuotes confuses compilation errors' line numbers -------------------------------------+------------------------------------- Reporter: yairchu | Owner: Type: bug | Status: new Priority: normal | Milestone: 7.12.1 Component: Compiler | Version: 6.12.3 (Parser) | Keywords: Resolution: | Architecture: Operating System: Unknown/Multiple | Unknown/Multiple Type of failure: Incorrect | Test Case: warning at compile-time | quasiquotation/T4150 Blocked By: | Blocking: Related Tickets: | Differential Revisions: -------------------------------------+------------------------------------- Comment (by Thomas Miedema <thomasmiedema@…>): In [changeset:"f72074ec85edd06867587698be4f3db48d0658d0/ghc"]: {{{ #!CommitTicketReference repository="ghc" revision="f72074ec85edd06867587698be4f3db48d0658d0" Fix quasiquotation test (#4150) }}} -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/4150#comment:15> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

Re: [GHC] #4150: CPP+QuasiQuotes confuses compilation errors' line numbers
by GHC 23 Mar '15

23 Mar '15

#4150: CPP+QuasiQuotes confuses compilation errors' line numbers -------------------------------------+------------------------------------- Reporter: yairchu | Owner: Type: bug | Status: new Priority: normal | Milestone: 7.12.1 Component: Compiler | Version: 6.12.3 (Parser) | Keywords: Resolution: | Architecture: Operating System: Unknown/Multiple | Unknown/Multiple Type of failure: Incorrect | Test Case: warning at compile-time | quasiquotation/T4150 Blocked By: | Blocking: Related Tickets: | Differential Revisions: -------------------------------------+------------------------------------- Changes (by thomie): * priority: low => normal Comment: There is a test already actually: `quasiquotation/T4150`. It is currently marked as expect_broken. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/4150#comment:14> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

[GHC] #10146: Clang CPP adds extra newline character
by GHC 23 Mar '15

23 Mar '15

#10146: Clang CPP adds extra newline character -------------------------------------+------------------------------------- Reporter: mpickering | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.8.4 Keywords: cpp | Operating System: MacOS X Architecture: | Type of failure: None/Unknown Unknown/Multiple | Blocked By: Test Case: | Related Tickets: Blocking: | Differential Revisions: | -------------------------------------+------------------------------------- Running the following command (taken from the settings file) {{{ cat ImportsSemi.hs | gcc -E -undef -traditional -Wunicode -Wno-invalid-pp- token -Wno-unicode - > out.hs }}} on any file results in a file which has an extra newline character appended to the end. This result is different from when `gcc` is used as the preprocessor, in this case no extra newline is appended. I appreciate that this isn't important to most users but it is important for ghc-exactprint. With the extra newline character the EOF marker is moved one line further down. When we come to output the AST, we also get an extra newline at the bottom of the file which breaks roundtripping. {{{ > gcc --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn) Target: x86_64-apple-darwin14.0.0 Thread model: posix }}} -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10146> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 4

Re: [GHC] #7098: GHC 7.4.1 reports an internal error and core dumps while using DPH
by GHC 23 Mar '15

23 Mar '15

#7098: GHC 7.4.1 reports an internal error and core dumps while using DPH -------------------------------------+------------------------------------- Reporter: Prasanna | Owner: benl Type: bug | Status: new Priority: normal | Milestone: Component: Data Parallel | Version: 7.4.1 Haskell | Keywords: DPH Resolution: | Architecture: Operating System: Unknown/Multiple | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: 7330 | Blocking: Related Tickets: | Differential Revisions: -------------------------------------+------------------------------------- Changes (by thomie): * component: Compiler => Data Parallel Haskell * milestone: 7.12.1 => -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/7098#comment:6> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 0

[GHC] #9849: GHC readme.md seems out of date
by GHC 23 Mar '15

23 Mar '15

#9849: GHC readme.md seems out of date -------------------------------------+------------------------------------- Reporter: carter | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.8.3 Keywords: | Operating System: Architecture: Unknown/Multiple | Unknown/Multiple Difficulty: Unknown | Type of failure: Blocked By: | None/Unknown Related Tickets: | Test Case: | Blocking: | Differential Revisions: -------------------------------------+------------------------------------- https://github.com/ghc/ghc/blob/89f5f314e32c3e80c71f4b3dcc8835ae74d7d57f/RE… still mentions using sync-all script, but the wiki docs say its deprecated https://ghc.haskell.org/trac/ghc/wiki/Building/SyncAll -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/9849> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 1

[GHC] #8727: HLearn test on ubuntu Precise x64 within vagrant Box
by GHC 23 Mar '15

23 Mar '15

#8727: HLearn test on ubuntu Precise x64 within vagrant Box ----------------------------------+-------------------------- Reporter: teuffy | Owner: Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.6.3 Keywords: | Operating System: Linux Architecture: x86_64 (amd64) | Type of failure: Other Difficulty: Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | ----------------------------------+-------------------------- ghc: panic! (the 'impossible' happened) (GHC version 7.6.3 for x86_64-unknown-linux): loadArchive "/home/vagrant/.cabal/lib/x86_64-linux- ghc-7.6.3/HLearn-2.0.0.0/libHSHLearn-2.0.0.0.a": failed {{{ import HLearn.Algebra import Control.DeepSeq import HLearn.Models.Distributions import Statistics.Distribution.Normal dataset = [1,2,3,4,5,6] --dist = train dataset :: Normal Double data Marble = Red | Green | Blue | White deriving (Read,Show,Eq,Ord) simonBag :: [Marble] simonBag = [Red, Red, Red, Green, Blue, Green, Red, Blue, Green, Green, Red, Red, Blue, Red, Red, Red, White] simonDist = train simonBag :: Categorical Double Marble }}} -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8727> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler

1 18