- Haskell-Cafe - Haskell.org

PLDI 2024 - Call for Participation (Early registration: May 15)
by Yao Li 03 Apr '24

03 Apr '24

Call for Participation for PLDI 2024, the ACM SIGPLAN Conference on Programming Language Design and Implementation! ------------------------------------------------------------------------ PLDI is a premier forum for programming language research, broadly construed, including design, implementation, theory, applications, and performance. Come join us, online or in Copenhagen, Denmark, to discuss the latest programming languages research! * Website : https://pldi24.sigplan.org/attending/registration * Time : Mon 24--Fri 28 June 2024 * Place : Radisson Blu Scandinavia, Amager Boulevard 70, 2300 Copenhagen S, Denmark ### Important dates * Early Registration: 15th of May, 2024 ### Important rates (Registration rates include a 25% VAT; The prices displayed include tax) Registration rates (in-person) On or before 15 May, 2024 After 15 May, 2024 Regular (ACM or SIGPLAN member) €770.00 €850.00 Regular (non-member) €850.00 €935.00 Student (ACM or SIGPLAN member) €425.00 €505.00 Student (non-member) €475.00 €540.00 Registration rates (virtual) On or before 15 May, 2024 After 15 May, 2024 Regular (ACM or SIGPLAN member) €37.50 €50.00 Regular (non-member) €37.50 €50.00 Student (ACM or SIGPLAN member) €37.50 €50.00 Student (non-member) €37.50 €50.00 1-Day Pass (Co-Located events) On or before 15 May, 2024 After 15 May, 2024 Regular (ACM or SIGPLAN member) €225.00 €250.00 Regular (non-member) €250.00 €275.00 Student (ACM or SIGPLAN member) €150.00 €175.00 Student (non-member) €175.00 €200.00 ### Co-located events: Co-located Conferences: - ISMM, ACM SIGPLAN International Symposium on Memory Management https://conf.researchr.org/home/ismm-2024 - LCTES, ACM SIGPLAN/SIGBED International Conference on Languages, Compilers, and Tools for Embedded Systems https://pldi24.sigplan.org/home/LCTES-2024 Workshops: - ARRAY, the Array Programming Workshop https://pldi24.sigplan.org/home/ARRAY-2024 - CP, International Workshop on Choreographic Programming https://pldi24.sigplan.org/home/cp-2024 - EGRAPHS, the E-Graph Research, Applications, Practices, and Human-factors Symposium https://pldi24.sigplan.org/home/egraphs-2024 - Infer, the Infer Practitioners Workshop https://pldi24.sigplan.org/home/infer-2024 - PLMW, the Programming Languages Mentoring Workshop https://pldi24.sigplan.org/track/PLMW-PLDI-2024 - PODELSKI, PLDI 2024 Workshop Honoring Andreas Podelsk https://pldi24.sigplan.org/home/podelski-2024 - RTFM, Red-Hot Topics in Faculty Mentoring https://pldi24.sigplan.org/home/rtfm-2024 - SOAP, the ACM SIGPLAN International Workshop on the State Of the Art in Program Analysis https://pldi24.sigplan.org/home/SOAP-2024 - Sparse, the Sparse workshop (formerly CTSTA) https://pldi24.sigplan.org/home/sparse-2024 - WQS, Workshop on Quantum Software https://pldi24.sigplan.org/home/wqs-2024 Tutorials: https://pldi24.sigplan.org/track/pldi-2024-tutorials - Algorithms and Applications for Provable Repair of Deep Neural Networks Aditya V. Thakur - Concurrent Algorithms in Kotlin Coroutines Nikita Koval - Democratizing DSL development with the BuildIt Framework Ajay Brahmakshatriya, Saman Amarasinghe - PODELSKI Thomas Wies, Martin Schäf, Andrey Rybalchenko - Quick and dirty development of static analyses with LiSA Luca Negrini, Pietro Ferrara - Static Code Analysis with SootUp Eric Bodden, Markus Schmidt, Jonas Klauke, Kadiray Karakaya, Stefan Schott Student Research Competition! https://pldi24.sigplan.org/track/pldi-2024-src ### Student Volunteering Sign up to be a Volunteer and help us make PLDI 2024 a great experience for all attendants! https://pldi24.sigplan.org/track/pldi-2024-student-volunteering Apply here: https://forms.gle/QB9Tdmhr9v9ZPGx9A. The deadline is 15th of April. Best regards, Yao Li, Ph.D., (He/Him) Assistant Professor, Computer Science Department, Portland State University

1 0

Announce: HsShellScript 3.6.4
by Volker Wysk 03 Apr '24

03 Apr '24

Hi! HsShellScript is a library that lets you do your Unix scripting in Haskell. It was outdated with respect to the supported compiler (meaning base- package) version, but now I've ported it to base >= 4.17.0.0 && < 5 (GHC 9.4/9.5). That's the recommended version (as of 2024-04-02). Here's the homepage: https://volker-wysk.de/hsshellscript/ Cheers, Volker

1 0

Hackage: "Build: PlanningFailed"
by Volker Wysk 03 Apr '24

03 Apr '24

Hello I'm fighting with Hackage. To make things short, I've published my HsShellScript library (was a package candidate before). Here's the library's Hackage page: https://hackage.haskell.org/package/hsshellscript-3.6.2 And there's a button labeled "Build: PlanningFailed". When I click on it, I get the following messages under "Build Log": -----snip----- Resolving dependencies... Error: cabal: Could not resolve dependencies: [__0] trying: hsshellscript-3.6.2 (user goal) [__1] next goal: base (dependency of hsshellscript) [__1] rejecting: base-4.18.1.0/installed-4.18.1.0 (conflict: hsshellscript => base>=4.13.0 && <4.14) [__1] skipping: base-4.19.1.0, base-4.19.0.0, base-4.18.2.0, base-4.18.1.0, base-4.18.0.0, base-4.17.2.1, base-4.17.2.0, base-4.17.1.0, base-4.17.0.0, 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 (has the same characteristics that caused the previous version to fail: excluded by constraint '>=4.13.0 && <4.14' from 'hsshellscript') [__1] rejecting: 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, hsshellscript) After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: base, hsshellscript -----snip----- Why does it reject the base library? The versions conflict, but why does it think the version should be base-4.18.1.0? The library compiles okay on my machine (using "cabal build"). I have this in the hsshellscript.cabal file, under "build-depends:": base >= 4.13.0 && < 4.14 I've got this version information from calling "cabal gen-bounds". Cheers, Volker

7 20

Cabal: Can only one processor core be used?
by Volker Wysk 02 Apr '24

02 Apr '24

Hi I've searched the web and the cabal user guide on how to use more processor cores for compilation via cabal. I couldn't find anything. It looks like only one processor core can be used with cabal, even though (I've read on the web) GHC supports parallel compilation. Cabal compilation times can be a pain. It can't be that you can use only one processor core with cabal, can it ..? Cheers, Volker

7 9

Cabal install fails, don't understand why
by Volker Wysk 31 Mar '24

31 Mar '24

Hi I've migrated my HsShellScript library to Cabal 3.0 and now I get an error when I try to install it: -----snip----- desktop /usr/local/src/hsshellscript $ cabal install --user Wrote tarball sdist to /usr/local/src/hsshellscript/dist-newstyle/sdist/hsshellscript-3.6.0.tar.gz Resolving dependencies... Error: cabal: Cannot build the executables in the package hsshellscript because it does not contain any executables. Check the .cabal file for the package and make sure that it properly declares the components that you expect. -----snip----- I don't understand this error message. Why does it think it should build executables? There aren't any. It's a library only. The hsshellscript.cabal file is this (comments and description removed): -----snip----- cabal-version: 3.0 name: hsshellscript version: 3.6.0 synopsis: Using Haskell for Unix shell scripting tasks Description: (...) Homepage: http://www.volker-wysk.de/hsshellscript/ license: LGPL-3.0-or-later license-file: LICENSE author: Volker Wysk maintainer: post(a)volker-wysk.de Copyright: (C) 2021-2024 by Volker Wysk category: System build-type: Simple extra-doc-files: CHANGELOG.md, README.md Extra-source-files: Makefile common warnings Library import: warnings Exposed-Modules: HsShellScript HsShellScript.Args HsShellScript.Paths HsShellScript.Shell Other-Modules: HsShellScript.Commands HsShellScript.GetOpt HsShellScript.Misc HsShellScript.ProcErr Default-Extensions: DeriveDataTypeable, ForeignFunctionInterface, RecordWildCards, ScopedTypeVariables, NamedFieldPuns, StandaloneDeriving Build-depends: base ^>=4.13.0.0, directory >= 1.3.6 && < 1.4, unix >= 2.7.2 && < 2.8, parsec >= 3.1.14 && < 3.2, random >= 1.1 && < 1.2 hs-source-dirs: src C-Sources: src/cbits/hsshellscript.c default-language: Haskell2010 source-repository head type: git location: https://gitlab.com/volkerwysk/hsshellscript.git -----snip----- Thanks for any help! Cheers, Volker

5 9

PostDoc in using Formal Methods for finding security vulnerabilities and misconfigurations in business-process-driven systems (Deadline: 2024-04-18)
by Achim D. Brucker 30 Mar '24

30 Mar '24

Dear all, As part of a US funded project, we have an exciting opportunity for a PostDoc in the Security and Trust of Advanced Systems Group at the University of Exeter (UK) to work applying formal methods to enterprise systems: We will use formal methods (e.g., model checking, SMT solving, interactive theorem proving), to analyze business-process-driven (enterprise) systems (e.g., business logic and workflows described a BPMN models). A particular focus will be the analysis of complex compositions of workflows within one organization as well as across multiple organizations. In particular, we will develop novel techniques to detect faults and vulnerabilities (that can be exploited by both internal and external attackers) in complex business-process-driven systems, contributing to protecting critical workflows such as manufacturing or logistics. In such environments, attackers can exploit such faults and vulnerabilities to cause all kinds of harm such as direct financial losses or causing the production of safety or security critical products to stop. Overall, the project aims to develop automated techniques for assessing the risk of business process or workflows as well as finding and mitigating such attacks. This is a unique opportunity for somebody wanting to use/apply formal methods to the security of large enterprise systems. More information and application details can be found at: * <https://jobs.exeter.ac.uk/hrpr_webrecruitment/wrd/run/etrec179gf.open?WVID=…> Application deadline is the 18th of April 2024. Please contact me for more details. Best, Achim -- Prof. Achim Brucker | Chair in Cybersecurity & Head of Group | University of Exeter https://www.brucker.ch | https://logicalhacking.com/blog @adbrucker | @logicalhacking

1 0

[ANNOUNCE] GHC 9.10.1-alpha2 is now available
by Ben Gamari 29 Mar '24

29 Mar '24

The GHC developers are very pleased to announce the availability of the second alpha release of GHC 9.10.1. Binary distributions, source distributions, and documentation are available at https://downloads.haskell.org/ghc/9.10.1-alpha2 We hope to have this release available via ghcup shortly. GHC 9.10 will bring 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 ([linear let]) * 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 [status]. 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-alpha2/docs/users_guide/9.10.1-not… [status]: 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 [ticket]: https://gitlab.haskell.org/ghc/ghc/-/issues/new

1 0

Volunteers for ICFP 2024 Artifact Evaluation Committee (AEC)
by Benoit Montagu 25 Mar '24

25 Mar '24

Dear all, We are looking for motivated people to be members of the ICFP 2024 Artifact Evaluation Committee (AEC). Students, researchers and people from the industry or the free software community are all welcome. The artifact evaluation process aims to improve the quality and reproducibility of research artifacts for ICFP papers. In case you want to nominate someone else (students, colleagues, etc.), please send them the nomination form. Nomination form: https://forms.gle/KJAjtDzhm5VLxjVf9 Deadline for nominations: Mon April 8th 2024 For more information, see the AEC webpage: https://icfp24.sigplan.org/track/icfp-2024-artifact-evaluation The primary responsibility of committee members is to review the artifacts submitted corresponding to the already conditionally accepted papers in the main research track. In particular, run the associated tool or benchmark, check whether the results in the paper can be reproduced, and inspect the tool and the data. We expect evaluation of one artifact to take about a full day. Each committee member will receive 2 to 3 artifacts to review. All of the AEC work will be done remotely/online. The AEC will work in June, with the review work happening between June 5th and July 5th. Come join us in improving the quality of research in our field! Best, the Artifact Evaluation chairs: Quentin Stiévenart and Benoît Montagu

1 0

Requesting For Comments for a new simple-dsp library
by Tristan Cacqueray 21 Mar '24

21 Mar '24

Dear cafe and Dr. Henning Thielemann, I'd like to propose a new package named simple-dsp. I couldn't figure out how to use the existing dsp library, so I made my own version featuring a little GUI to try the code in realtime. I'd be happy to contribute this work directly to dsp. My goal is to be able to extract sensible discrete values from a sound input at 60 Hz for video production. I implemented low/band/high pass filters to compute 3 RMS volumes, but the values I'm getting are not sharp enough, e.g. the band pass picks the low end. Ideally I would extract the transient events of the percusive sound and the note pitch of the melodic elements. I have very little understanding of DSP, and I'm sure there are better ways to achieve this goal, so I would appreciate it if someone more experienced could take a look: * Doc: https://tristancacqueray.github.io/simple-dsp/ * Candidate: https://hackage.haskell.org/package/simple-dsp-0.1/candidate * Forum: https://discourse.haskell.org/t/rfc-a-new-simple-dsp-library/9094 Thanks in advance, -Tristan

2 3

my ancient hackage account
by Keith Sheppard 21 Mar '24

21 Mar '24

Hi All, I wrote https://hackage.haskell.org/package/txt-sushi a long long time ago. I'd like to clean some things up and make some improvements. I tried to use the password recovery tool but it said it "wasn't available" for this account. Maybe because it's so old? Can anyone suggest how to recover the account? Thank you, Keith

2 1