- ghc-devs - Haskell.org

Looking for recent works on STG
by Rodrigo Mesquita 26 May '24

26 May '24

Dear all, Do you know of any recent works on the STG? In particular, I am looking for a result connecting STG's execution and Core’s call-by-need semantics when written in structural operational semantics style. Nonetheless, I’m also interested in possibly more recent formulations of STG (e.g. a mechanized one?) beyond the original paper. Cheers Rodrigo Mesquita

3 3

Question about -G RTS flag
by chessai 23 May '24

23 May '24

The docs for -G state: ``` ... Anything larger than about 4 is probably not a good idea unless your program runs for a *long* time, because the oldest generation will hardly ever get collected. ``` What is a "*long*" time?

2 1

Priorities for upcoming GHC releases
by Zubin Duggal 21 May '24

21 May '24

Hi all, We detail our plans for upcoming GHC releases in a new blog post: https://www.haskell.org/ghc/blog/20240521-ghc-release-priorities.html The summary is that we will prioritise work on the 9.10, 9.6 and master branches over work on the 9.8 branch for the coming few months due to time and resource constraints. This does not mean that we are dropping support for GHC 9.8, but that releases in this series might be made at a slower pace than usual. Cheers, Zubin.

1 0

Haddock now lives full-time in the GHC repository
by Hécate 17 May '24

17 May '24

Hello devs, As of today, Haddock now lives in the GHC repository, and not anymore as a submodule from another Gitlab repository which itself was rebased on top of a Github repository. You are encouraged to migrate our currently opened PRs to the GHC repo. If you have any trouble, please do ping me on Matrix (@acidalia:matrix.org), on GitLab (@kleidukos), or by email directly. Read more here: https://discourse.haskell.org/t/haddock-now-lives-in-the-ghc-repository/9576 My thanks to Ben Gamari who was essential in making this migration happen! Cheers, Hécate -- Hécate ✨ 🐦: @TechnoEmpress IRC: Hecate WWW: https://glitchbra.in RUN: BSD

1 0

account approval
by Davide Pancotto 16 May '24

16 May '24

Hello, I registered on gitlab as davide-pn because I want to report a bug. If you want to know it, you can approve it.

4 4

GHC notes plugin for Haskell language server
by Jan van Brügge 13 May '24

13 May '24

Hi all, a few days ago, version 2.8.0.0 of HLS was released and with that the new notes plugin. With this, you can use "Go to Definition" not only on Haskell types and identifiers, but also on Note references and you editor will jump to the relevant file and the position of the full note. Some of you might remember that I created the initial proof of concept at last year's ZuriHac/GHC contributor's Workshop. TL;DR: Update HLS and you dont need to search for notes any more. Cheers, Jan

3 2

GHC 9.10.1 is now available
by Ben Gamari 10 May '24

10 May '24

The GHC developers are very pleased to announce the release of GHC 9.10.1. Binary distributions, source distributions, and documentation are available at [downloads.haskell.org] and shortly via [GHCup]. GHC 9.10 brings a number of new features and improvements, including: * The introduction of the `GHC2024` language edition, building upon `GHC2021` with the addition of a number of widely-used extensions. * Partial implementation of the [GHC Proposal #281], allowing visible quantification to be used in the types of terms. * [Extension] of LinearTypes to allow linear `let` and `where` bindings * The implementation of the [exception backtrace proposal], allowing the annotation of exceptions with backtraces, as well as other user-defined context * Further improvements in the info table provenance mechanism, reducing code size to allow IPE information to be enabled more widely * Javascript FFI support in the WebAssembly backend * Improvements in the fragmentation characteristics of the low-latency non-moving garbage collector. * ... and many more A full accounting of changes can be found in the [release notes]. As always, GHC's release status, including planned future releases, can be found on the [GHC Wiki]. We would like to thank GitHub, IOG, the Zw3rk stake pool, Well-Typed, Tweag I/O, Serokell, Equinix, SimSpace, the Haskell Foundation, and other anonymous contributors whose on-going financial and in-kind support has facilitated GHC maintenance and release management over the years. Finally, this release would not have been possible without the hundreds of open-source contributors whose work comprise this release. As always, do give this release a try and open a [ticket] if you see anything amiss. [release notes]: https://downloads.haskell.org/ghc/9.10.1/docs/users_guide/9.10.1-notes.html [GHC Wiki]: https://gitlab.haskell.org/ghc/ghc/-/wikis/GHC-status [exception backtrace]: https://github.com/ghc-proposals/ghc-proposals/pull/330 [GHC Proposal #281]: https://github.com/ghc-proposals/ghc-proposals/pull/281 [linear let]: https://github.com/ghc-proposals/ghc-proposals/pull/624 [downloads.haskell.org] https://downloads.haskell.org/ghc/9.10.1 [ticket]: https://gitlab.haskell.org/ghc/ghc/-/issues/new [GHCup]: https://www.haskell.org/ghcup/

1 0

Reasoning on unicode static data compression at GHC-side
by Serge S. Gulin 10 May '24

10 May '24

Hi, dear ghc-devs subscribers! Propose a discussion about unicode size https://gitlab.haskell.org/ghc/ghc/-/issues/24789. It seems we should do nothing with it in code in the general case but it has its own approaches on how to control the size of resulting bundles/executions. -- Serge S. Gulin https://gitlab.haskell.org/gulin.serge

1 0

[ghc-9.10-rc] foldl' ambiguities in several packages
by Shayne Fletcher 10 May '24

10 May '24

using the ghc-9.10 release candidate, at least all of text-short, unordered-containers and vector-stream fail to compile with ambiguities around the export of symbol `foldl'`. example: ``` unordered-containers> [1 of 8] Compiling Data.HashMap.Internal.Array unordered-containers> /private/var/folders/rj/q93vlym52875_k7nwz_c3wth0000gn/T/stack-da6d6d11ecd50280/unordered-containers-0.2.19.1/Data/HashMap/Internal/Array.hs:66:7-12: error: [GHC-87543] unordered-containers> Ambiguous occurrence ‘foldl'’. unordered-containers> It could refer to unordered-containers> either ‘Prelude.foldl'’, unordered-containers> imported from ‘Prelude’ at Data/HashMap/Internal/Array.hs:(97,1)-(98,48) unordered-containers> (and originally defined in ‘ghc-internal-9.1001.0:GHC.Internal.Data.Foldable’), unordered-containers> or ‘Data.HashMap.Internal.Array.foldl'’, unordered-containers> defined at Data/HashMap/Internal/Array.hs:380:1. unordered-containers> | unordered-containers> 66 | , foldl' unordered-containers> | ^^^^^^ ``` so far i've found all such errors can be overcome by qualification at the export site but is this expected? -- Shayne Fletcher

2 1

2nd Call for Papers: ACM Workshop on Functional Software Architecture [Deadline June 3]
by michael.sperber＠active-group.de 24 Apr '24

24 Apr '24

====================================================================== *** FUNARCH 2024 -- CALL FOR PAPERS *** Second ACM SIGPLAN Workshop on Functional Software Architecture - FP in the Large 6th September 2024, Milan, Italy Co-located with ICFP 2024 https://functional-architecture.org/events/funarch-2024/ ====================================================================== TIMELINE: Paper submission 3rd June 2024 Author notification 30th June 2024 Camera ready copy 18th July 2024 Workshop 6th Sept 2024 BACKGROUND: "Functional Software Architecture" refers to methods of construction and structure of large and long-lived software projects that are implemented in functional languages and released to real users, typically in industry. The goals for the workshop are: - To assemble a community interested in software architecture techniques and technologies specific to functional programming; - To identify, categorize, and document topics relevant to the field of functional software architecture; - To connect the functional programming community to the software architecture community to cross-pollinate between the two. The workshop follows on from the Functional Software Architecture open space that was held at ICFP 2022 in Slovenia. SCOPE: The workshop seeks submissions in a range of categories: - You're a member of the FP community and have thought about how to support programming in the large, for example by framing functional ideas in architectural terms or vice verse, comparing different languages in terms of their architectural capabilities, clarifying architectural roles played by formal methods, proof assistants and DSLs, or observing how functional concepts are used in other language and architecture communities. Great, submit a research paper! - You're a member of the architecture community, and have thought about how your discipline might help functional programmers, for example by applying domain-driven design, implementing hexagonal architecture, or designing self-contained systems. Excellent, submit a research paper! - You've worked on a large project using functional programming, and it's worked out well, or terribly, or a mix of both; bonus points for deriving architectural principles from your experience. Wonderful, submit an experience report! - You know a neat architectural idiom or pattern that may be useful to others developing large functional software systems. Fabulous, submit an architectural pearl! - You have something that doesn't fit the above categories, but that still relates to functional software architecture, such as something that can be written up, or that could be part of the workshop format like a panel debate or a fishbowl. Superb, submit to the open category! Research papers should explain their research contributions in both general and technical terms, identifying what has been accomplished, explaining why it is significant, and relating it to previous work, and to other languages where appropriate. Experience reports and architectural pearls need not necessarily report original research results. The key criterion for such papers is that they make a contribution from which others can benefit. It is not enough simply to describe a large software system, or to present ideas that are specific to a particular system. Open category submissions that are not intended for publication are not required to follow the formatting guidelines, and can submit in PDF, word or plain text format as preferred. Not knowing what kinds of submissions we will receive, we cannot be specific as to how they will be evaluated. However, submissions that seem likely to stimulate discussion around practices in functional architecture are encouraged. If you are unsure whether your contribution is suitable, or if you need any kind of help with your submission, please email the program chairs at <funarch2024(a)easychair.org>. Papers must be submitted by 3rd June 2024 using the EasyChair submission page: https://easychair.org/my/conference?conf=funarch2024 Formatting: submissions intended for publication must be in PDF format and follow the ACM SIGPLAN style guidelines, using the acmart format and the sigplan sub-format. Please use the review option when submitting, as this enables line numbers for easy reference in reviews. For further details, see SIGPLAN's author information: http://www.sigplan.org/Resources/Author/#acmart-format If your submission is not a research paper, please mark this using a subtitle (Experience Report, Architectural Pearl, Open Category). Length: submissions must adhere to the limits specified below. However, there is no requirement or expectation that all pages are used, and authors are encouraged to strive for brevity. Research papers 5 to 12+ pages Architectural pearls 5 to 12 pages Experience reports 3 to 6 pages Open category 1 to 6 pages Publication: The proceedings of FUNARCH 2024 will be published in the ACM Digital Library, and authors of accepted papers are required to agree to one of the standard ACM licensing options. Accepted papers must be presented at the workshop by one of the authors, but in special cases we may consider remote presentation. The official publication date is the date the papers are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work. PROGRAM CHAIRS: Mike Sperber (Active Group, Germany) Perdita Stevens (University of Edinburgh, UK) PROGRAM COMMITTEE: Annette Bieniusa (University of Kaiserslautern) Jeffrey Young (IOG) Will Crichton (Brown University) Isabella Stilkerich (Schaeffler Technologies AG) Kiko Fernandez-Reyes (Ericsson) Ryan Scott (Galois) Satnam Singh (Groq) Facundo Dominguez (Tweag) Ilya Sergey (University of Singapore) Martin Elsman (University of Copenhagen) Benjamin Pierce (University of Pennsylvania) Matthew Flatt (University of Utah) Nada Amin (Harvard University) Richard Eisenberg (Jane Street) WORKSHOP VENUE: The workshop will be co-located with the ICFP 2024 conference at the Fiera Milano Congressi, Milan, Italy.

1 0