- ghc-devs - Haskell.org

Coercing a `ByteArray#` into a `MutableByteArray#`
by Adithya Kumar 24 Jul '23

24 Jul '23

Hello all, I have a use-case where I want to convert `ByteArray#` to `MutableByteArray#` without the copy overhead. Is the underlying memory structure of `ByteArray#` and `MutableByteArray#` the same? If I can guarantee that I won't mutate my `MutableByteArray#`, can I use `unsafeCoerce#` on `ByteArray#` and treat it as `MutableByteArray#`? Best, Adithya

4 3

RFC Or patterns syntax: (p1 | p2) vs. (p1; p2)
by Sebastian Graf 24 Jul '23

24 Jul '23

Hi devs, I would like to invite you to provide arguments for or against the Or patterns syntax RFC `(p1; p2)` vs. `(p1 | p2)` over at this GH issue <https://github.com/ghc-proposals/ghc-proposals/issues/598>. *In particular, `(p1 | p2)` has a small lead over `(p1; p2)`*, but the latter will steal syntax from a hypothetical guards-in-patterns extension `(p | e)` as described here <https://gitlab.haskell.org/ghc/ghc/-/wikis/view-patterns-alternative>. I dismissed this point until Vlad made me aware <https://github.com/ghc-proposals/ghc-proposals/issues/598#issuecomment-1600…> of the fact that `f (a -> b)` *could* mean "a pattern match on the type constructor `(->)`" in a Dependent Haskell future. Apparently, the existence of the hypothetical guards-in-patterns extension was reason enough <https://github.com/ghc-proposals/ghc-proposals/issues/598#issuecomment-1600…> to exclude view patterns from GHC2021. Of course, `(p1; p2)` has issues of its own. Given how close this vote is, I want to make sure that you, the GHC devs, are aware of this issue and perhaps have a few minutes to formulate a (counter) argument or just leave your vote before we submit the winner in the actual amendment proposal, at which point it will be up to the GHC steering committee to decide. Thanks, Sebastian

1 0

ghc-9.4.6 is being prepared
by Matthew Pickering 24 Jul '23

24 Jul '23

Hi all, Zubin is preparing the 9.4.6 release so we expect to release it within the next two weeks. The focus of the release ot back-port the quite large number of fixes which are marked for backport to 9.4. https://gitlab.haskell.org/ghc/ghc/-/merge_requests?scope=all&state=opened&… Cheers, Matt

1 0

Request for approval of account
by Mark Seemann 18 Jul '23

18 Jul '23

Hello I’d like to report a bug in GHC because an error message tells me to do so. In order to do that, I’m trying to follow the guidelines in https://gitlab.haskell.org/ghc/ghc/-/wikis/report-a-bug, so I’ve created an account. The next step, as I understand it, is to use this mailing list to request approval for he account. I’m hereby doing that. TIA Mark Seemann

1 0

Why do the reverse binder swap transformation?
by Rodrigo Mesquita 14 Jul '23

14 Jul '23

Dear GHC devs, I’m wondering about the reverse binder swap transformation, the one in which we substitute occurrences of the case binder by occurrences of the scrutinee (when the scrut. is a variable): case x of z { r -> e } ===> case x of z { r -> e[x/z] } My question is: why do we do this transformation? An example in which this transformation is beneficial would be great too. The Note I’ve found about it, Note [Binder-swap during float-out], wasn’t entirely clear to me: 4. Note [Binder-swap during float-out] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In the expression case x of wild { p -> ...wild... } we substitute x for wild in the RHS of the case alternatives: case x of wild { p -> ...x... } This means that a sub-expression involving x is not "trapped" inside the RHS. And it's not inconvenient because we already have a substitution. Note that this is EXACTLY BACKWARDS from the what the simplifier does. The simplifier tries to get rid of occurrences of x, in favour of wild, in the hope that there will only be one remaining occurrence of x, namely the scrutinee of the case, and we can inline it. Many thanks, Rodrigo

3 3

Exact-print info in the the HsSyn syntax tree
by Simon Peyton Jones 13 Jul '23

13 Jul '23

Dear GHC developers Could you please look at #23447 Where should "tokens" live <https://gitlab.haskell.org/ghc/ghc/-/issues/23447>? In brief, the question is whether we want to have: data HsExpr p = .... | HsLet (XLet p) (HsLocalBinds p) (LHsExpr p) or data HsExpr p = .... | HsLet (XLet p) (HsToken "let" p) (HsLocalBinds p) (HsToken "in" p) (LHsExpr p) In the former, if a client wants HsTokes to track the precise source locations of the "let" and "in" keywords, they'd have to put it in the TTG extension field; in the latter, this information is in *every* syntax tree. At the moment we have some of each, which is not satisfactory. We need to decide a policy and stick to it. If you use HsSyn, HsExpr, HsPat etc, in any way, you should have an opinion. Please do express it. At the moment we have only a few voices so we risk deciding without enough evidence and use-cases. Comments with specific use-cases and examples would be particularly helpful. Thanks! Simon

2 3

New spurious failure bot is running on GitLab
by Bryan Richter 13 Jul '23

13 Jul '23

Today I've deployed a new version of my retry service. I think I've worked out most of the kinks, so I'm going to leave it running overnight and see how it goes. In the worst case, it might crash and die, in which case spurious failures will not get retried until I come back and fix it tomorrow morning, Europe time. In the best case, the service will just keep doing what the old one did, with two improvements: 1. If the same job keeps failing, it will give up retries. 2. If sending a retry command to GitLab itself fails, those will also be retried a few times. -Bryan "Who retries the retryer?" - Juvenal, probably

1 0

Usage of Template Haskell quotes in GHC source tree vs. usage of GHC as a library
by Gergő Érdi 13 Jul '23

13 Jul '23

Hi, A recent commit 983ce55815f2dd57f84ee86eee97febf7d80b470 starts using TemplateHaskellQuotes in the GHC codebase. It seems this is at odds with using GHC as a library, a la ghc-lib. The `ghc-lib` approach is to basically take the module hierarchy from the `compiler/` subtree, and compile it as a completely vanilla Haskell library, with no direct attachment to the host GHC version. This enables using e.g. GHC 9.4 to compile a program using the GHC 9.6 API, and so on. In particular, it also makes it very easy to apply patches to the version of GHC used as a library, since in this setup it doesn’t need to be able to bootstrap. So what is the problem with using TemplateHaskellQuotes? The problem is the dependency on the template-haskell package. When a module inside GHC-as-a-library containing TH quotes is compiled, the quotes are translated into applications of the constructors defined by the *host* GHC’s TH package. But because GHC is tightly coupled to the TH support library, GHC-as-a-library needs to ship with its own internal version of the library. So the code that tries to process the results of these quotes is using the *target* GHC’s TH definitions. And that leads to a conflict: code like leftName :: Namel leftName = ‘Left is now a type mismatch between the type of `’Left` being template-haskell-2.19.0.0:Language.Haskell.TH.Syntax.Name (example when using GHC 9.4.5 as the host) and the type of `leftName` being ghc-lib-9.9.20230712:Language.Haskell.TH.Syntax.Name (example when the target version is built from recent `master`). Currently, `ghc-lib-gen` has a pre-processing step on the GHC source tree that replaces these quotations with applications containing direct references to the target TH constructors: https://github.com/digital-asset/ghc-lib/blob/ab01fb2b4d1e3a9338390e9c10ccd… but I am worried that this is very fragile. So any ideas on how to tackle this situation better? Thanks, Gergo

3 2

Can't build nofib
by Simon Peyton Jones 12 Jul '23

12 Jul '23

Friends With a clean HEAD I can't build nofib. See below. What should I do? Thanks Simon (cd nofib; cabal v2-run -- nofib-run --compiler=`pwd`/../_build/stage1/bin/ghc --output=`date -I`) Resolving dependencies... Error: cabal: Could not resolve dependencies: [__0] trying: nofib-0.1.0.0 (user goal) [__1] next goal: base (dependency of nofib) [__1] rejecting: base-4.18.0.0/installed-4.18.0.0 (conflict: nofib => base>=4.5 && <4.17) [__1] skipping: base-4.18.0.0, base-4.17.1.0, base-4.17.0.0 (has the same characteristics that caused the previous version to fail: excluded by constraint '>=4.5 && <4.17' from 'nofib') [__1] rejecting: base-4.16.4.0, base-4.16.3.0, base-4.16.2.0, base-4.16.1.0, base-4.16.0.0, base-4.15.1.0, base-4.15.0.0, base-4.14.3.0, base-4.14.2.0, base-4.14.1.0, base-4.14.0.0, base-4.13.0.0, base-4.12.0.0, base-4.11.1.0, base-4.11.0.0, base-4.10.1.0, base-4.10.0.0, base-4.9.1.0, base-4.9.0.0, base-4.8.2.0, base-4.8.1.0, base-4.8.0.0, base-4.7.0.2, base-4.7.0.1, base-4.7.0.0, base-4.6.0.1, base-4.6.0.0, base-4.5.1.0, base-4.5.0.0, base-4.4.1.0, base-4.4.0.0, base-4.3.1.0, base-4.3.0.0, base-4.2.0.2, base-4.2.0.1, base-4.2.0.0, base-4.1.0.0, base-4.0.0.0, base-3.0.3.2, base-3.0.3.1 (constraint from non-upgradeable package requires installed instance) [__1] fail (backjumping, conflict set: base, nofib) After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: base, nofib make: *** [/home/simonpj/code/Makefile-spj:39: nofib] Error 1

3 6

Call for Talks: Haskell Implementors' Workshop 2023 (deadline extension)
by Ryan Scott 10 Jul '23

10 Jul '23

TL;DR: The submission deadline for the 2023 Haskell Implementors' Workshop has been extended to June 16. ================================== ACM SIGPLAN Haskell Implementors' Workshop https://icfp23.sigplan.org/home/hiw-2023 Seattle, Washington, United States, September 4, 2023 Co-located with ICFP 2023 https://icfp23.sigplan.org/ Important dates --------------- Deadline: July 16, 2023 (AoE) (extended) Notification: August 4, 2023 Workshop: September 4, 2023 The 15th Haskell Implementors' Workshop is to be held alongside ICFP 2023 this year in Seattle. It is a forum for people involved in the design and development of Haskell implementations, tools, libraries, and supporting infrastructure to share their work and to discuss future directions and collaborations with others. Talks and/or demos are proposed by submitting an abstract, and selected by a small program committee. There will be no published proceedings. The workshop will be informal and interactive, with open spaces in the timetable and room for ad-hoc discussion, demos, and short lightning talks. Scope and target audience ------------------------- It is important to distinguish the Haskell Implementors' Workshop from the Haskell Symposium which is also co-located with ICFP 2023. The Haskell Symposium is for the publication of Haskell-related research. In contrast, the Haskell Implementors' Workshop will have no proceedings -- although we will aim to make talk videos, slides, and presented data available with the consent of the speakers. The Implementors' Workshop is an ideal place to describe a Haskell extension, describe works-in-progress, demo a new Haskell-related tool, or even propose future lines of Haskell development. Members of the wider Haskell community are encouraged to attend the workshop -- we need your feedback to keep the Haskell ecosystem thriving. Students working with Haskell are especially encouraged to share their work. The scope covers any of the following topics. There may be some topics that people feel we've missed, so by all means submit a proposal even if it doesn't fit exactly into one of these buckets: * Compilation techniques * Language features and extensions * Type system implementation * Concurrency and parallelism: language design and implementation * Performance, optimisation and benchmarking * Virtual machines and run-time systems * Libraries and tools for development or deployment Talks ----- We invite proposals from potential speakers for talks and demonstrations. We are aiming for 20-minute talks with 5 minutes for questions and changeovers. We want to hear from people writing compilers, tools, or libraries, people with cool ideas for directions in which we should take the platform, proposals for new features to be implemented, and half-baked crazy ideas. Please submit a talk title and abstract of no more than 300 words. Submissions can be made via HotCRP at https://icfp-hiw23.hotcrp.com until July 16 (anywhere on earth). We will also have a lightning talks session. These have been very well received in recent years, and we aim to increase the time available to them. Lightning talks should be ~7mins and are scheduled on the day of the workshop. Suggested topics for lightning talks are to present a single idea, a work-in-progress project, a problem to intrigue and perplex Haskell implementors, or simply to ask for feedback and collaborators. Program Committee ----------------- * Gergő Érdi (Standard Chartered Bank) * Sebastian Graf (Karlsruhe Institute of Technology) * Wen Kokke (University of Strathclyde) * Ryan Scott (Galois, Inc.) * Rebecca Skinner (Mercury) * Li-yao Xia (University of Edinburgh) Contact ------- * Ryan Scott <ryan.gl.scott at gmail.com>

1 1