ghc-devs  

Messages by Thread

• • RE: Can NamedFieldPuns be added to `GHC.LanguageExtensions.Types.Extension`? Simon Peyton Jones via ghc-devs
  • Re: Can NamedFieldPuns be added to `GHC.LanguageExtensions.Types.Extension`? Alfredo Di Napoli
  • Re: Can NamedFieldPuns be added to `GHC.LanguageExtensions.Types.Extension`? Richard Eisenberg
  • Re: Can NamedFieldPuns be added to `GHC.LanguageExtensions.Types.Extension`? Edward Kmett
  • Re: Can NamedFieldPuns be added to `GHC.LanguageExtensions.Types.Extension`? Alfredo Di Napoli
• Marking ParsedModule fragments as non-user-originating Erdi, Gergo via ghc-devs
  • RE: Marking ParsedModule fragments as non-user-originating Simon Peyton Jones via ghc-devs
  • RE: Marking ParsedModule fragments as non-user-originating Erdi, Gergo via ghc-devs
• Trying to speedup GHC compile times...Help! Young, Jeff
  • Re: Trying to speedup GHC compile times...Help! Ben Gamari
  • RE: Trying to speedup GHC compile times...Help! Simon Peyton Jones via ghc-devs
  • Re: Trying to speedup GHC compile times...Help! Richard Eisenberg
  • RE: Trying to speedup GHC compile times...Help! Simon Peyton Jones via ghc-devs
  • Re: Trying to speedup GHC compile times...Help! Christiaan Baaij
  • RE: Trying to speedup GHC compile times...Help! Simon Peyton Jones via ghc-devs
  • Re: Trying to speedup GHC compile times...Help! Matthew Pickering
  • Re: Trying to speedup GHC compile times...Help! Viktor Dukhovni
  • RE: Trying to speedup GHC compile times...Help! Simon Peyton Jones via ghc-devs
  • Re: Trying to speedup GHC compile times...Help! Jeffrey Young
  • Re: Trying to speedup GHC compile times...Help! Jaro Reinders
  • Re: Trying to speedup GHC compile times...Help! Brandon Allbery
  • Re: Trying to speedup GHC compile times...Help! Jeffrey Young
• Writing GHC plugin to modify AST despite failure to type-check Evan Relf
  • Re: Writing GHC plugin to modify AST despite failure to type-check Zubin Duggal
  • Re: Writing GHC plugin to modify AST despite failure to type-check Christiaan Baaij
  • Re: Writing GHC plugin to modify AST despite failure to type-check Zubin Duggal
  • Re: Writing GHC plugin to modify AST despite failure to type-check Zubin Duggal
• Loading a typechecked module and then using it immediately as a package Erdi, Gergo via ghc-devs
  • Re: Loading a typechecked module and then using it immediately as a package Matthew Pickering
  • Re: Loading a typechecked module and then using it immediately as a package ÉRDI Gergő
  • RE: [External] Re: Loading a typechecked module and then using it immediately as a package Erdi, Gergo via ghc-devs
  • RE: [External] Re: Loading a typechecked module and then using it immediately as a package Erdi, Gergo via ghc-devs
  • Re: Loading a typechecked module and then using it immediately as a package Sylvain Henry
  • Re: Loading a typechecked module and then using it immediately as a package Erdi, Gergo via ghc-devs
  • RE: Loading a typechecked module and then using it immediately as a package Erdi, Gergo via ghc-devs
  • Re: Loading a typechecked module and then using it immediately as a package Matthew Pickering
  • Re: Loading a typechecked module and then using it immediately as a package Erdi, Gergo via ghc-devs
  • Re: Loading a typechecked module and then using it immediately as a package Erdi, Gergo via ghc-devs
• Is there a way to prevent reboxing in W/W (due to OPAQUE pragma proposal) Christiaan Baaij
  • RE: Is there a way to prevent reboxing in W/W (due to OPAQUE pragma proposal) Simon Peyton Jones via ghc-devs
  • Re: Is there a way to prevent reboxing in W/W (due to OPAQUE pragma proposal) Sebastian Graf
• Final Call for Talks: Haskell Implementors' Workshop @ ICFP'21 Ningning Xie
• Re: An error occurred Ben Gamari
• Breaking changes to the base library Harendra Kumar
  • Re: Breaking changes to the base library Ben Gamari
  • Re: Breaking changes to the base library Chris Smith
  • Re: Breaking changes to the base library Edward Kmett
  • Re: Breaking changes to the base library Oleg Grenrus
  • Re: Breaking changes to the base library Carter Schonwald
  • Re: Breaking changes to the base library Harendra Kumar
  • Re: Breaking changes to the base library Richard Eisenberg
  • Re: Breaking changes to the base library Zubin Duggal
• Error message degradation for (<= :: Nat -> Nat -> Constraint) in GHC 9.2+ Christiaan Baaij
  • Re: Error message degradation for (<= :: Nat -> Nat -> Constraint) in GHC 9.2+ Sam Derbyshire
  • Re: Error message degradation for (<= :: Nat -> Nat -> Constraint) in GHC 9.2+ Carter Schonwald
  • Re: Error message degradation for (<= :: Nat -> Nat -> Constraint) in GHC 9.2+ Adam Gundry
  • Re: Error message degradation for (<= :: Nat -> Nat -> Constraint) in GHC 9.2+ Christiaan Baaij
  • RE: Error message degradation for (<= :: Nat -> Nat -> Constraint) in GHC 9.2+ Simon Peyton Jones via ghc-devs
  • Re: Error message degradation for (<= :: Nat -> Nat -> Constraint) in GHC 9.2+ Christiaan Baaij
• Is simplified subsumption really necessary? Chris Smith
  • RE: Is simplified subsumption really necessary? Simon Peyton Jones via ghc-devs
  • Re: Is simplified subsumption really necessary? John Ericson
  • RE: Is simplified subsumption really necessary? Simon Peyton Jones via ghc-devs
  • Re: Is simplified subsumption really necessary? John Ericson
  • RE: Is simplified subsumption really necessary? Simon Peyton Jones via ghc-devs
  • Re: Is simplified subsumption really necessary? Adam Sandberg Eriksson
• CI Status Update Ben Gamari
  • Re: CI Status Update Ben Gamari
• Anyone ever wondered what our favourite merge bot is up to? Matthew Pickering
  • Re: Anyone ever wondered what our favourite merge bot is up to? Richard Eisenberg
  • Re: Anyone ever wondered what our favourite merge bot is up to? Matthew Pickering
  • Re: Anyone ever wondered what our favourite merge bot is up to? Vladislav Zavialov
• Rewriting plugins: request for feedback Sam Derbyshire
  • Re: Rewriting plugins: request for feedback Sam Derbyshire
  • Re: Rewriting plugins: request for feedback Sam Derbyshire
  • Re: Rewriting plugins: request for feedback Christiaan Baaij
  • Re: Rewriting plugins: request for feedback Sam Derbyshire
  • Re: Rewriting plugins: request for feedback Sam Derbyshire
  • Re: Rewriting plugins: request for feedback Sam Derbyshire
  • Re: Rewriting plugins: request for feedback Carter Schonwald
  • Re: Rewriting plugins: request for feedback Sam Derbyshire
  • Re: Rewriting plugins: request for feedback Sam Derbyshire
• abstract interpreter for GHC Core or STG Csaba Hruska
  • Re: abstract interpreter for GHC Core or STG Carter Schonwald
  • Re: abstract interpreter for GHC Core or STG Carter Schonwald
  • Re: abstract interpreter for GHC Core or STG Csaba Hruska
  • RE: abstract interpreter for GHC Core or STG Simon Peyton Jones via ghc-devs
  • Re: abstract interpreter for GHC Core or STG Carter Schonwald
  • Re: abstract interpreter for GHC Core or STG Csaba Hruska
  • Re: abstract interpreter for GHC Core or STG Carter Schonwald
  • Re: abstract interpreter for GHC Core or STG Csaba Hruska
  • Re: abstract interpreter for GHC Core or STG Csaba Hruska
• [Haskell] [ANNOUNCE] GHC 8.10.5 released Zubin Duggal
  • Re: [Haskell] [ANNOUNCE] GHC 8.10.5 released Zubin Duggal
• [CI] macOS builds Moritz Angermann
• ghcup failed Simon Peyton Jones via ghc-devs
  • Re: ghcup failed Tom Ellis
  • RE: ghcup failed Simon Peyton Jones via ghc-devs
  • Re: ghcup failed Viktor Dukhovni
  • Re: ghcup failed Karel Gardas
• Give MonadTrans a QuantifiedConstraints superclass Baldur Blöndal
  • Re: Give MonadTrans a QuantifiedConstraints superclass chessai
• value of documenting error messages? Richard Eisenberg
  • Re: value of documenting error messages? Alec Theriault
  • RE: value of documenting error messages? Simon Peyton Jones via ghc-devs
  • Re: value of documenting error messages? Tom Ellis
  • Re: value of documenting error messages? Ruben Astudillo
  • Re: value of documenting error messages? Carter Schonwald
  • Re: value of documenting error messages? Mario Carneiro
  • Re: value of documenting error messages? Tom Ellis
  • Re: value of documenting error messages? Richard Eisenberg
  • Re: value of documenting error messages? Tom Ellis
  • Re: value of documenting error messages? Richard Eisenberg
  • Re: value of documenting error messages? Tom Ellis
  • Re: value of documenting error messages? Jakob Brünker
  • Re: value of documenting error messages? Alan & Kim Zimmerman
  • Re: value of documenting error messages? Carter Schonwald
  • Re: value of documenting error messages? Bryan Richter
  • RE: value of documenting error messages? Simon Peyton Jones via ghc-devs
• GitLab downtime Ben Gamari
  • Re: GitLab downtime Ben Gamari
  • Re: GitLab downtime Ben Gamari
  • Re: GitLab downtime Richard Eisenberg
  • Re: GitLab downtime Ben Gamari
  • Re: GitLab downtime Ben Gamari
  • Re: GitLab downtime Vladislav Zavialov
  • Re: GitLab downtime Shayne Fletcher
  • Re: GitLab downtime Matthew Pickering
  • Re: GitLab downtime Giorgio Marinelli
  • Re: GitLab downtime Ben Gamari
• GHC releases and versions Sylvain Henry
  • Re: GHC releases and versions Iavor Diatchki
• Errors in haddock git fetch Simon Peyton Jones via ghc-devs
  • Re: Errors in haddock git fetch Sylvain Henry
  • Re: Errors in haddock git fetch Alan & Kim Zimmerman
• Ampere A1 instances for builder/marge? Karel Gardas
• Productivity Tip from mpickering Matthew Pickering
  • Re: Productivity Tip from mpickering Richard Eisenberg
  • Re: Productivity Tip from mpickering Oleg Grenrus
• GHC head, profiling with -O2 does not work Harendra Kumar
  • Re: GHC head, profiling with -O2 does not work Ben Gamari
• GHC and the future of Freenode Ben Gamari
  • Re: GHC and the future of Freenode Sebastian Graf
  • Re: GHC and the future of Freenode Jack Hill
  • Re: GHC and the future of Freenode Carter Schonwald
  • Re: GHC and the future of Freenode Ben Gamari
  • Re: GHC and the future of Freenode Alex Rozenshteyn
  • Re: GHC and the future of Freenode Carter Schonwald
  • Re: GHC and the future of Freenode Mario Carneiro
  • Re: GHC and the future of Freenode Alex Rozenshteyn
  • Re: GHC and the future of Freenode Artem Pelenitsyn
  • Re: GHC and the future of Freenode Carter Schonwald
  • Re: GHC and the future of Freenode Viktor Dukhovni
  • Re: GHC and the future of Freenode Brandon Allbery
  • Re: GHC and the future of Freenode John Ericson
  • Re: GHC and the future of Freenode Janek Stolarek
  • Re: GHC and the future of Freenode Jakub Zalewski
  • Re[2]: GHC and the future of Freenode Sebastian Graf
  • Re: GHC and the future of Freenode Chris Smith
  • Re: GHC and the future of Freenode Jens Petersen
  • Re: GHC and the future of Freenode Moritz Angermann
  • Re: GHC and the future of Freenode Iavor Diatchki
  • Re: GHC and the future of Freenode Ben Gamari
  • Re: GHC and the future of Freenode Iavor Diatchki
  • Re: GHC and the future of Freenode Imants Cekusins
  • Re: GHC and the future of Freenode Chris Smith
  • Re: GHC and the future of Freenode Shivam Gupta
  • Re: GHC and the future of Freenode John Ericson
  • Re: GHC and the future of Freenode Matthew Pickering
  • Re: GHC and the future of Freenode John Ericson
• Darwin CI Status Matthew Pickering
  • Re: Darwin CI Status Moritz Angermann
  • Re: Darwin CI Status Matthew Pickering
• Coding style: Using StandaloneKindSignatures in GHC Baldur Blöndal
  • Re: Coding style: Using StandaloneKindSignatures in GHC Sebastian Graf
  • Re: Coding style: Using StandaloneKindSignatures in GHC Hécate
  • Re: Coding style: Using StandaloneKindSignatures in GHC Oleg Grenrus
  • Re: Coding style: Using StandaloneKindSignatures in GHC Richard Eisenberg
  • Re: Coding style: Using StandaloneKindSignatures in GHC Hécate
  • Re: Coding style: Using StandaloneKindSignatures in GHC Baldur Blöndal
  • Re: Coding style: Using StandaloneKindSignatures in GHC Carter Schonwald
  • Re: Coding style: Using StandaloneKindSignatures in GHC Ben Gamari
  • Re: Coding style: Using StandaloneKindSignatures in GHC Chris Smith
  • Re: Coding style: Using StandaloneKindSignatures in GHC Richard Eisenberg
  • RE: Coding style: Using StandaloneKindSignatures in GHC Simon Peyton Jones via ghc-devs
  • Re: Coding style: Using StandaloneKindSignatures in GHC Oleg Grenrus
  • Re: Coding style: Using StandaloneKindSignatures in GHC chessai
  • Re: Coding style: Using StandaloneKindSignatures in GHC Carter Schonwald
  • RE: Coding style: Using StandaloneKindSignatures in GHC Simon Peyton Jones via ghc-devs
• Second Call for Talks: Haskell Implementors' Workshop @ ICFP'21 Ningning Xie
• an issue tracker for better error messages Richard Eisenberg
• ZuriHac 2021 - GHC Track - Call for Contributions Andreas Herrmann
  • RE: ZuriHac 2021 - GHC Track - Call for Contributions Simon Peyton Jones via ghc-devs
  • Re: ZuriHac 2021 - GHC Track - Call for Contributions Andreas Herrmann
• Warnings Simon Peyton Jones via ghc-devs
  • Re: Warnings Ben Gamari
• structured error messages Richard Eisenberg
  • Re: structured error messages Chris Smith
  • Re: structured error messages Richard Eisenberg
  • Re: structured error messages John Ericson

• Earlier messages
• Later messages