- Haskell-Cafe - Haskell.org

Re. Haskell Usage
by Rishiyur Nikhil 15 Nov '23

15 Nov '23

> Haskell was "more for academic purposes", The Bluespec Hardware Design Languages BSV (Bluespec SystemVerilog) and BH (Bluespec Haskell) digital hardware circuit design have been in industrial production and commercial use for over 20 years now. They have been used inside ST Micro, Texas Instruments, IBM, Qualcomm, Google, Galois and other companies, for ASIC and FPGA products and for high-level hardware prototyping and architecture exploration. The BSV and BH languages are themselves heavily inspired by Haskell. The 'bsc' compiler for BSV and BH is written entirely in Haskell, and has been in continuous use/development/maintenance/improvement for 20 years, and constitutes about 125K lines of Haskell. The 'bsc' compiler was open-sourced a few years ago and continues to be actively used and maintained: https://github.com/B-Lang-org/bsc The Haskell code for the compiler is in the src/ directory. Nikhil

1 0

Haskell Usage
by Henrique Caldeira 15 Nov '23

15 Nov '23

Good Evening from Portugal, I write to you about the usage of Haskell because I had a professor recommending me Erlang instead because Haskell was "more for academic purposes", which left me wondering if all my time spent was spent only for curiosity sake. I want to know how true my professor's statement is. I am very passionate about Haskell, although I admit the ecosystem can be confusing sometimes (for example, when to use cabal or stack, which versions of packages to use in order to avoid conflicts, or simply installing them through nixos or arch can be a learning process). Would love to hear your thoughts about all of this and thank you with all my heart. Lastly, all these wonderings are asked in a curious, "wanting to learn more" mindset. Kind regards, Henrique Caldeira

7 6

Journal of Functional Programming - Call for PhD Abstracts
by Graham Hutton 13 Nov '23

13 Nov '23

Dear all, If you or one of your students recently completed a PhD (or Habilitation) in the area of functional programming, please submit the dissertation abstract for publication in JFP: simple process, no refereeing, open access, 200+ published to date, deadline 30th November 2023. Please share! Best wishes, Graham Hutton ============================================================ CALL FOR PHD ABSTRACTS Journal of Functional Programming Deadline: 30th November 2023 http://tinyurl.com/jfp-phd-abstracts ============================================================ PREAMBLE: Many students complete PhDs in functional programming each year. As a service to the community, twice per year the Journal of Functional Programming publishes the abstracts from PhD dissertations completed during the previous year. The abstracts are made freely available on the JFP website, i.e. not behind any paywall. They do not require any transfer of copyright, merely a license from the author. A dissertation is eligible for inclusion if parts of it have or could have appeared in JFP, that is, if it is in the general area of functional programming. The abstracts are not reviewed. Please submit dissertation abstracts according to the instructions below. We welcome submissions from both the student and the advisor/supervisor although we encourage them to coordinate. Habilitation dissertations are also eligible for inclusion. ============================================================ SUBMISSION: Please submit the following information to Graham Hutton <graham.hutton(a)nottingham.ac.uk> by 30th November 2023. o Dissertation title: (including any subtitle) o Student: (full name) o Awarding institution: (full name and country) o Date of award: (month and year; depending on the institution, this may be the date of the viva, corrections being approved, graduation ceremony, or otherwise) o Advisor/supervisor: (full names) o Dissertation URL: (please provide a permanently accessible link to the dissertation if you have one, such as to an institutional repository or other public archive; links to personal web pages should be considered a last resort) o Dissertation abstract: (plain text, maximum 350 words; you may use \emph{...} for emphasis, but we prefer no other markup or formatting; if your original abstract exceeds the word limit, please submit an abridged version within the limit) Please do not submit a copy of the dissertation itself, as this is not required. JFP reserves the right to decline to publish abstracts that are not deemed appropriate. ============================================================ PHD ABSTRACT EDITOR: Graham Hutton School of Computer Science University of Nottingham Nottingham NG8 1BB United Kingdom ============================================================ This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please contact the sender and delete the email and attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. Email communications with the University of Nottingham may be monitored where permitted by law.

1 0

Trouble installing example code for Parallel and Concurrent Programming in Haskell
by David Banas 12 Nov '23

12 Nov '23

I just picked up a copy of “Parallel and Concurrent Programming in Haskell”. And I’m trying to follow the instructions on p.4 for getting the examples installed, but having trouble: [23-11-10 9:49] dbanas@Davids-Air-M2:~/prj % cabal unpack parconc-examples Downloading parconc-examples-0.4.8 Downloaded parconc-examples-0.4.8 Unpacking to parconc-examples-0.4.8/ [23-11-10 9:50] dbanas@Davids-Air-M2:~/prj % pushd parconc-examples-0.4.8 ~/prj/parconc-examples-0.4.8 ~/prj ~ [23-11-10 9:50] dbanas@Davids-Air-M2:~/prj/parconc-examples-0.4.8 % cabal install --only-dependencies cabal: Could not resolve dependencies: [__0] trying: parconc-examples-0.4.8 (user goal) [__1] next goal: base (dependency of parconc-examples) [__1] rejecting: base-4.17.2.0/installed-4.17.2.0 (conflict: parconc-examples => base>=4.5 && <4.14) [__1] skipping: base-4.19.0.0, base-4.18.1.0, base-4.18.0.0, 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.5 && <4.14' from 'parconc-examples') [__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, parconc-examples) After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: base, parconc-examples Thanks, -db

4 5

[ANNOUNCE] GHC 9.4.8 is now available
by Zubin Duggal 10 Nov '23

10 Nov '23

The GHC developers are happy to announce the availability of GHC 9.4.8. Binary distributions, source distributions, and documentation are available on the [release page](/download_ghc_9_4_8.html). This release is primarily a bugfix release addressing a few issues found in the 9.4 series. These include: * A fix for a recompilation checking bug where GHC may miss changes in transitive dependencies when deciding to relink a program (#23724). * A fix for a code generator bug on AArch64 platforms resulting in invalid conditional jumps (#23746). * Support for `-split-sections` on Windows. * Enabling `-split-sections` for various Linux and Windows binary distributions, enabling GHC to produce smaller binaries on these platforms. * And a few other fixes A full accounting of changes can be found in the [release notes]. As some of the fixed issues do affect correctness users are encouraged to upgrade promptly. We would like to thank Microsoft Azure, GitHub, IOG, the Zw3rk stake pool, Well-Typed, Tweag I/O, Serokell, Equinix, SimSpace, 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. Happy compiling! -Zubin [ticket]: https://gitlab.haskell.org/ghc/ghc/-/issues/new [release notes]: https://downloads.haskell.org/~ghc/9.4.8/docs/users_guide/9.4.8-notes.html

1 0

[ANN] mig-0.2 library to build servers and clients
by Anton Kholomiov 09 Nov '23

09 Nov '23

I’m happy to announce the latest release of mig-0.2 <https://github.com/anton-k/mig> library. It is a library to write composable servers for simple / boring haskell. The main focus of this release is the ability to serve Swagger UI from the server with ease and ability to create clients from the same code as servers. I’m happy to confirm that both goals are reached with this release. The tutorial for the library <https://anton-k.github.io/mig/> was created. Also there are many other improvements: - OpenApi schema for servers - swagger servers support (we can add swagger to server with one line of code: withSwagger def server ) - clients from the same code as servers - redesign of internal types - redesign of DSL for routes - many ergonomic improvements - packages for extra utils - split of mig package to several packages: - mig <https://hackage.haskell.org/package/mig> - core - mig-wai <https://hackage.haskell.org/package/mig-wai> - rendering servers to wai apps - mig-client <https://hackage.haskell.org/package/mig-client> - clients - mig-extra <https://hackage.haskell.org/package/mig-extra> - extra utils - mig-server <https://hackage.haskell.org/package/mig-server> - mig servers with batteries - mig-swagger-ui <https://hackage.haskell.org/package/mig-swagger-ui> - swagger ui server - tutorial and quickstart guide <https://anton-k.github.io/mig/> on github pages - CI for repo with formatter, build and tests and update of docs on github pages The internal type for Servers was redesigned so that we assemble the handler function with API description at the same time. In the first release it was just a handler function under the hood. As a refresher mig <https://github.com/anton-k/mig> is a family of libraries to write lightweight, simple, type-safe and composable servers. It strives to be in the middle ground between scotty and servant. To be composable, flexible and type-safe as servant and simple and lightweight in concepts as scotty. One thing that interesting to think about as Server is a first-class value and all servers have the same type and we have just a small number of functions to compose them (they are link server to path and make alternative routes with Monoid) it’s interesting to explore the possibility of creation small grain-like servers for typical tasks. For example, a server can be a function from interfaces (logging, DB or something else) to server value and we can join them together on various paths. This idea is interesting to consider. Thanks to Ambros for contribution. Also I’d like to thank the authors of packages servant, servant-swagger-ui and servant-openapi3 packages for inspiration for my work in this release. Many lines of code are influenced by those packages. Links: - github <https://github.com/anton-k/mig> - tutorial <https://anton-k.github.io/mig/> - mig on hackage <https://hackage.haskell.org/package/mig> also see packages mig-server <https://hackage.haskell.org/package/mig-server> and mig-client <https://hackage.haskell.org/package/mig-client>. - examples <https://github.com/anton-k/mig/tree/main/examples/mig-example-apps> Cheers, Anton

1 0

[ANN] Copilot 3.17
by Ivan Perez 09 Nov '23

09 Nov '23

Hi everyone!! We are very excited to announce Copilot 3.17 [2]. Copilot is a stream-based EDSL in Haskell for writing and monitoring embedded C programs, with an emphasis on correctness and hard realtime requirements. Copilot is typically used as a high-level runtime verification framework, and supports temporal logic (LTL, PTLTL and MTL), clocks and voting algorithms. Copilotis being used at NASA in drone test flights. Through the NASA tool Ogma [1] (also written in Haskell), Copilot also serves as a runtime monitoring backend for NASA's Core Flight System, Robot Operating System (ROS2), and FPrime (the software framework used in the Mars Helicopter) applications. This release introduces compatibility with what4 versions up to 1.5.1, and replaces several functions in copilot-core. The second change is a breaking change: the functions replaced have been deprecated and new alternatives introduced instead. As always, we're releasing exactly 2 months since the last release. Our next release is scheduled for Jan 7th, 2024. In our last announcement, we mentioned that Copilot has received full approval for release as NASA Class D open-source software. Current emphasis is on increasing test coverage for the two remaining libraries without tests (copilot-libraries and copilot-theorem), removing unnecessary dependencies, hiding internal definitions, and formatting the code to meet our new coding standards. Users are encouraged to participate by opening issues and asking questions via our github repo [3]. There have been many updates on the Copilot front in the last few months. We'll be able to announce more soon. Stay tuned. Happy Haskelling! Ivan [1] https://github.com/nasa/ogma [2] https://github.com/Copilot-Language/copilot/releases/tag/v3.17 [3] https://github.com/Copilot-Language/copilot [4] https://hackage.haskell.org/package/copilot

1 0

Call for Contributions: BOB 2024 [March 15, Deadline Nov 17]
by Stefan Wehr 03 Nov '23

03 Nov '23

======================================================================== BOB Conference 2024 "What happens when we use what's best for a change?" https://bobkonf.de/2024/cfc.html Berlin, Mar 17 Call for Contributions Deadline: November 17, 2023 ======================================================================== You are actively engaged in advanced software engineering methods, solve ambitious problem with software and are open to cutting-edge innovation? Attend this conference, meet people that share your goals, and get to know the best software tools and technologies available today. We strive to offer a day full of new experiences and impressions that you can use to immediately improve your daily life as a software developer. If you share our vision and want to contribute, submit a proposal for a talk or tutorial! NOTE: The conference fee will be waived for presenters. Travel expenses will not be covered (for exceptions see "Speaker Grants"). Shepherding ----------- The program committee offers shepherding to all speakers. Shepherding provides speakers assistance with preparing their sessions. Specifically: - advice on structure and presentation - review of talk slides Speaker Grants -------------- BOB has Speaker Grants available to support speakers from groups under-represented in technology. We specifically seek women speakers, speakers of color, and speakers who are not able to attend the conference for financial reasons. Topics ------ We are looking for talks about best-of-breed software technology, e.g.: - functional programming - persistent data structures and databases - event-based modelling and architecture - "fancy types" (dependent types, gradual typing, linear types, ...) - formal methods for correctness and robustness - abstractions for concurrency and parallelism - metaprogramming - probabilistic programming - math and programming - controlled side effects - program synthesis - next-generation IDEs - effective abstractions for data analytics - … everything really that isn’t mainstream, but you think should be - … includeing rough ideas worth discussing. Presenters should provide the audience with information that is practically useful for software developers. Challenges ---------- Furthermore, we seek contributions on successful approaches for solving hard problems, for example: - bias in machine-learning systems - digital transformation in difficult settings - accessibiltity - systems with critical reliability requirements - ecologically sustainable software development We're especially interested in experience reports. Other topics are also relevant, e.g.: - introductory talks on technical background - overviews of a given field - demos and how-tos Requirements ------------ We accept proposals for presentations of 45 minutes (40 minutes talk + 5 minutes questions), as well as 90 minute tutorials for beginners. The language of presentation should be either English or German. Your proposal should include (in your presentation language of choice): - An abstract of max. 1500 characters. - A short bio/cv - Contact information (including at least email address) - A list of 3-5 concrete ideas of how your work can be applied in a developer's daily life - additional material (websites, blogs, slides, videos of past presentations, …) Organisation ------------ - Direct questions to konferenz at bobkonf dot de - Proposal deadline: November 17, 2023 - Notification: December 5, 2023 - Program: December 12, 2023 Submit here: https://pretalx.com/bob-2024/submit/ Program Committee ----------------- (more information here: https://bobkonf.de/2024/programmkomitee.html) - Matthias Fischmann, Wire - Matthias Neubauer, SICK AG - Nicole Rauch, Softwareentwicklung und Entwicklungscoaching - Michael Sperber, Active Group - Stefan Wehr, Hochschule Offenburg Scientific Advisory Board - Annette Bieniusa, TU Kaiserslautern - Torsten Grust, Uni Tübingen - Peter Thiemann, Uni Freiburg

1 0

Question on Lexing Haskell syntax
by Travis Athougies 02 Nov '23

02 Nov '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 According to the Haskell report [1] (See Note 5), a virtual `}` token is inserted if parsing the next token would cause a parse error and the indentation stack is non-empty. I'm trying to lex and parse Haskell source and this sort of interplay (which requires two-way communication between lexer and parser) makes it very difficult to write a conformant implementation. I can't change the standard (obviously), but I'm wondering if this is actually what GHC (de facto the only Haskell compiler) does, or if it applies some other rule. If so, does anyone know the exact mechanism of its implementation? I've been programming Haskell for more than a decade, and while I have an intuitive understanding of the indentation rules, I would have assumed the source could be lexed without also having a parser. In particular, the note seems to imply that the main purpose of this is to properly lex `let`/`in` bindings. Perhaps there's an alternate equivalent rule? Curious to hear other's thoughts. Travis [1] https://www.haskell.org/onlinereport/haskell2010/haskellch10.html#x17-17800… -----BEGIN PGP SIGNATURE----- iIsEARYKADMWIQRW81c55hOCXuY5k/H+BxaRGQDTjQUCZUGARhUcdHJhdmlzQGF0 aG91Z2llcy5uZXQACgkQ/gcWkRkA041W+wEA/7n5NejGTYu4O6N+Pt7Rn0bBRw6D 5D96idagahXqXioA/18hxYFpY45lWwB7pKCh83xQJu2Bcwkxj1xhhCEZBcoA =FrDy -----END PGP SIGNATURE-----

5 6

Munich Haskell Meeting, 2023-10-31 @ 19:30
by Leah Neukirchen 30 Oct '23

30 Oct '23

Dear all, Next week, our monthly Munich Haskell Meeting will take place again on Tuesday, October 31 at Iveria (Lindwurmstraße 159A) at 19h30. For details see here: http://muenchen.haskell.bayern/dates.html If you plan to join, please add yourself to this nuudel so we can reserve enough seats! It is OK to add yourself to the nuudel anonymously or pseudonymously. https://nuudel.digitalcourage.de/7ST4pxNRVj3rGLdO Everybody is welcome! cu, -- Leah Neukirchen <leah(a)vuxu.org> https://leahneukirchen.org/

2 1