- Haskell-Cafe - Haskell.org

2nd CfP: IFL 2018 (30th Symposium on Implementation and Application of Functional Languages)
by Jurriaan Hage 03 Apr '18

03 Apr '18

Hello, Please, find below the second call for papers for IFL 2018. Please forward these to anyone you think may be interested. Apologies for any duplicates you may receive. best regards, Jurriaan Hage Publicity Chair of IFL --- ================================================================================ IFL 2018 30th Symposium on Implementation and Application of Functional Languages University of Massachusetts Lowell, MA, USA September 5th-7th, 2018 http://iflconference.org ================================================================================ ### Scope The goal of the IFL symposia is to bring together researchers actively engaged in the implementation and application of functional and function-based programming languages. IFL 2018 will be a venue for researchers to present and discuss new ideas and concepts, work in progress, and publication-ripe results related to the implementation and application of functional languages and function-based programming. Topics of interest to IFL include, but are not limited to: - language concepts - type systems, type checking, type inferencing - compilation techniques - staged compilation - run-time function specialization - run-time code generation - partial evaluation - (abstract) interpretation - metaprogramming - generic programming - automatic program generation - array processing - concurrent/parallel programming - concurrent/parallel program execution - embedded systems - web applications - (embedded) domain specific languages - security - novel memory management techniques - run-time profiling performance measurements - debugging and tracing - virtual/abstract machine architectures - validation, verification of functional programs - tools and programming techniques - (industrial) applications ### Keynote Speakers * Adam Chlipala, Massachusetts Institute of Technology CSAIL * Arjun Guha, University of Massachusetts Amherst ### Submissions and peer-review Differently from previous editions of IFL, IFL 2018 solicits two kinds of submissions: * Regular papers (12 pages including references) * Draft papers for presentations ('weak' limit between 8 and 15 pages) Regular papers will undergo a rigorous review by the program committee, and will be evaluated according to their correctness, novelty, originality, relevance, significance, and clarity. A set of regular papers will be conditionally accepted for publication. Authors of conditionally accepted papers will be provided with committee reviews along with a set of mandatory revisions. Regular papers not accepted for publication will be considered as draft papers, at the request of the author. Draft papers will be screened to make sure that they are within the scope of IFL, and will be accepted for presentation or rejected accordingly. Prior to the symposium: Authors of conditionally accepted papers and accepted presentations will submit a pre-proceedings version of their work that will appear in the draft proceedings distributed at the symposium. The draft proceedings does not constitute a formal publication. We require that at least one of the authors present the work at IFL 2018. After the symposium: Authors of conditionally accepted papers will submit a revised versions of their paper for the formal post-proceedings. The program committee will assess whether the mandatory revisions have been adequately addressed by the authors and thereby determines the final accept/reject status of the paper. Our interest is to ultimately accept all conditionally accepted papers. If you are an author of a conditionally accepted paper, please make sure that you address all the concerns of the reviewers. Authors of accepted presentations will be given the opportunity to incorporate the feedback from discussions at the symposium and will be invited to submit a revised full article for the formal post-proceedings. The program committee will evaluate these submissions according to their correctness, novelty, originality, relevance, significance, and clarity, and will thereby determine whether the paper is accepted or rejected. ### Publication The formal proceedings will appear in the International Conference Proceedings Series of the ACM Digital Library. At no time may work submitted to IFL be simultaneously submitted to other venues; submissions must adhere to ACM SIGPLAN's republication policy: http://www.sigplan.org/Resources/Policies/Republication ### Important dates Submission of regular papers: May 25, 2018 Submission of draft papers: July 17, 2018 Regular and draft papers notification: July 20, 2018 Deadline for early registration: August 8, 2018 Submission of pre-proceedings version: August 29, 2018 IFL Symposium: September 5-7, 2018 Submission of papers for post-proceedings: November 7, 2018 Notification of acceptance: December 22, 2018 Camera-ready version: February 10, 2019 ### Submission details All contributions must be written in English. Papers must use the ACM two columns conference format, which can be found at: http://www.acm.org/publications/proceedings-template Authors submit through EasyChair: https://easychair.org/conferences/?conf=ifl2018 ### Peter Landin Prize The Peter Landin Prize is awarded to the best paper presented at the symposium every year. The honored article is selected by the program committee based on the submissions received for the formal review process. The prize carries a cash award equivalent to 150 Euros. ### Organization and Program committee Chairs: Jay McCarthy & Matteo Cimini, University of Massachusetts Lowell, USA Program Committee: * Arthur Chargueraud, Inria, FR * Ben Delaware, Purdue University, USA * Christos Dimoulas, Northwestern University, USA * David Darais, University of Vermont, USA * Dominic Orchard, University of Kent, UK * Ekaterina Komendantskaya, Heriot-Watt University, UK * Garrett Morris, University of Kansas, USA * Heather Miller, EPFL & Northeastern University, CH & USA * Jeremy Yallop, University of Cambridge, UK * Keiko Nakata, SAP Innovation Center Potsdam, DE * Laura Castro, University of A Coruna, ESP * Magnus Myreen, Chalmers University of Technology, SWE * Natalia Chechina, Bournemouth University, UK * Peter Achten, Radboud Universiteit Nijmegen, NL * Peter-Michael Osera, Grinnell College, USA * Richard Eisenberg, Bryn Mawr College, USA * Trevor McDonell, University of New South Wales, AUS * Yukiyoshi Kameyama, University of Tsukuba, JAP ### Venue The 30th IFL is organized by the University of Massachusetts Lowell. The City of Lowell is located at the heart of the Merrimack Valley just 30 miles northwest of Boston. Lowell can be easily reached by train or taxi. See the website for more information on the venue. ### Acknowledgments This call-for-papers is an adaptation and evolution of content from previous instances of IFL. We are grateful to prior organizers for their work, which is reused here. A part of IFL 2018 format and CFP language that describes conditionally accepted papers has been adapted from call-for-papers of OOPSLA conferences.

1 0

WST 2018 - 2nd Call for Papers (submission: April 15, 2018)
by Salvador Lucas 03 Apr '18

03 Apr '18

========================================================================== WST 2018 - Call for Papers 16th International Workshop on Termination July 18-19, 2017, Oxford, United Kingdom http://wst2018.webs.upv.es/ ========================================================================== The Workshop on Termination (WST) traditionally brings together, in an informal setting, researchers interested in all aspects of termination, whether this interest be practical or theoretical, primary or derived. The workshop also provides a ground for cross-fertilization of ideas from the different communities interested in termination (e.g., working on computational mechanisms, programming languages, software engineering, constraint solving, etc.). The friendly atmosphere enables fruitful exchanges leading to joint research and subsequent publications. The workshop is held as part of the 2018 Federated Logic Conference (FLoC 2018) http://www.floc2018.org/ IMPORTANT DATES: * submission deadline: April 15, 2018 * notification: May 15, 2018 * final version due: May 31, 2018 * workshop: July 18-19, 2018 TOPICS: The 16th International Workshop on Termination welcomes contributions on all aspects of termination. In particular, papers investigating applications of termination (for example in complexity analysis, program analysis and transformation, theorem proving, program correctness, modeling computational systems, etc.) are very welcome. Topics of interest include (but are not limited to): * abstraction methods in termination analysis * certification of termination and complexity proofs * challenging termination problems * comparison and classification of termination methods * complexity analysis in any domain * implementation of termination methods * non-termination analysis and loop detection * normalization and infinitary normalization * operational termination of logic-based systems * ordinal notation and subrecursive hierarchies * SAT, SMT, and constraint solving for (non-)termination analysis * scalability and modularity of termination methods * termination analysis in any domain (lambda calculus, declarative programming, rewriting, transition systems, etc.) * well-founded relations and well-quasi-orders COMPETITION: Since 2003, the catalytic effect of WST to stimulate new research on termination has been enhanced by the celebration of the Termination Competition and its continuously developing problem databases containing thousands of programs as challenges for termination analysis in different categories, see http://termination-portal.org/wiki/Termination_Competition In 2018, the Termination Competition will run in parallel with FLoC 2018. More details will be provided in a dedicated announcement on the competition. PROGRAM COMMITTEE: Cristina Borralleras - U. de Vic Ugo Dal Lago - U. degli Studi di Bologna Carsten Fuhs - Birkbeck, U. of London Samir Genaim - U. Complutense de Madrid Juergen Giesl - RWTH Aachen Raul Gutiérrez - U. Politecnica de València Keiichirou Kusakari - Gifu University Salvador Lucas (chair) - U. Politecnica de Valencia Fred Mesnard - U. de La Reunion Aart Middeldorp - U. of Innsbruck Albert Rubio - U. Politecnica de Catalunya Rene Thiemann - U. of Innsbruck Caterina Urban - ETH Zürich INVITED SPEAKERS: tba SUBMISSION: Submissions are short papers/extended abstracts which should not exceed 5 pages. There will be no formal reviewing. In particular, we welcome short versions of recently published articles and papers submitted elsewhere. The program committee checks relevance and provides additional feedback for each submission. The accepted papers will be made available electronically before the workshop. Papers should be submitted electronically via the submission page: https://easychair.org/conferences/?conf=wst2018 Please, use LaTeX and the LIPIcs style file http://drops.dagstuhl.de/styles/lipics/lipics-authors.tgz to prepare your submission.

1 0

vector-sized: (//) Finites to Ints?
by David Banas 03 Apr '18

03 Apr '18

When did the vector-sized (//) operator change from expecting Finites to expecting Ints?

1 0

[ANNOUNCE] GHC 8.4.2-rc1 now available
by Ben Gamari 03 Apr '18

03 Apr '18

Hello everyone, The GHC team is proud to announce the first release candidate of 8.4.2. the source distribution, binary distributions, and documentation are available at https://downloads.haskell.org/~ghc/8.4.2-rc1 This release follows so closely to 8.4.1 due to a number last-minute bug-fixes that didn't quite make it into 8.4.1. This includes fixes for: * #14705, the interpreter being broken on some systems * #14779, where the compiler produces invalid code when used with -g * #14891, where a selection of GHC testsuite cases fail on OS X * #5129, where the simplifier would incorrectly reorder evaluation in under some conditions. Since this is a relatively small bugfix release we are bypassing the alpha releases and moving right to the release candidate stage. If all goes well the final release will be cut next week. Happy testing Cheers, - Ben

2 2

Architecture for reflex based applications
by Robert Klotzner 02 Apr '18

02 Apr '18

Hi there! I did a little write up about structuring reflex applications, which seems to work out really well for me. Check it out here: https://github.com/gonimo/gonimo/blob/master/front/doc/Gonimo-Architecture.… I would love to hear your thoughts! Best regards, Robert

1 0

json-autotype 1.1.2, and type-providers initiative
by Michal J Gajda 02 Apr '18

02 Apr '18

Hi, I am pleased to announce new version of json-autotype. Highlights of the version: 1. GHC 8.4 support. 2. Preliminary support for Elm output (with more Haskell-family languages coming) 3. Peter Simons has joined the team as official maintainer. 4. Ask us anything on Gitter: https://gitter.im/dataHaskell/json-autotype Json-Autotype team, and Data Haskell Frames team is also pleased to announce `type-providers` initiative that aims to provide standard API for type providers for Haskell family of languages. (Please join us on Gitter: https://gitter.im/dataHaskell/type-providers and https://gitter.im/dataHaskell/DataFrames) -- Cheers Michal J. Gajda

1 0

Haskell mailing list etiquette
by Niklas Hambüchen 02 Apr '18

02 Apr '18

Dear mailing list participants, I recently discovered a document that contains, neatly enumerated, all the rules that we as a community follow today when discussing Haskell topics. Please direct Haskell newcomers to it as early as possible, so that they can learn our mode of working upfront, and don't have to discover it bit by bit. For everybody's convenience, I here are the key points: * When possible, refer all matters to committees, for "further study and consideration." Attempt to make the committees as large as possible. * Bring up irrelevant issues as frequently as possible. * Ask endless questions or engage in long correspondence about such orders. Quibble over them when you can. * Haggle over precise wordings of communications, minutes, resolutions. * Refer back to matters decided upon at the last meeting and attempt to re-open the question of the advisability of that decision. * Advocate "caution". Be "reasonable" and urge your fellow-conferees to be "reasonable" and avoid haste which might result in embarrassments or difficulties later on. * Be worried about the propriety of any decision - raise the question of whether such action as is contemplated lies within the jurisdiction of the group or whether it might conflict with the policy of some higher echelon. You can find the full list of rules here (refer to page 28): https://www.cia.gov/news-information/featured-story-archive/2012-featured-s… Best, Niklas

2 1

Proposal: Professionalizing GHC Development
by Gershom B 01 Apr '18

01 Apr '18

Fellow Haskellers, Recently there has been much work into creating a better and more professional GHC development process, including in the form of DevOps infrastructure, scheduled releases and governance, etc. But much remains to be done. There continues to be concern about the lack of use of industry-standard tools. For example, GHC development is tied to Phabricator, which is a custom product originally developed for in-house use by an obscure startup. GHC development is documented on a wiki still -- ancient technology, not appropriate for 2018. Wiki syntax for documentation needs to be replaced by the only modern standard -- github flavored markdown. Trac itself is ancient technology, dating to 2003, well before anybody knew how to program real software. It provides no support for all the most important aspects of software development -- Kanban boards, sprint management, or even burndown charts. What is necessary is an integrated solution that holistically addresses all aspects of development, fostering a DevOps culture, embracing cloud-first, agile-first, test-first, disrupt-first principles, and with an ironclad SLA. Rather than homegrown solutions, we need a GHC development process that utilizes tools and procedures already familiar to regular developers. Cross-sectional feature comparison analysis yields a clear front-runner -- Visual Studio Team Services. VSTS is a recognized Leader in the Gartner Magic Quadrant for Enterprise Agile Planning tools. It lets us migrate from custom git hosting to a more reliable source control system -- Team Foundation Version Control. By enforcing the locking of checked-out files, we can prevent the sorts of overlap between different patches that occur in the current distributed version management system, and coordinate tightly between developers, enabling and fostering T-shaped skills. Team Build also lets us migrate from antiquated makefiles to modern, industry-standard technology -- XML descriptions of build processes that integrate automatically with tracking of PBIs (product backlog items), and one-button release management. In terms of documentation, rather than deal with the subtleties of different markdown implementations and the confusing world of restructured text, we can utilize the full power of Word, including SharePoint integration as well as Office 365 capabilities, and integration with Microsoft Teams, the chat-based workspace for collaboration. This enables much more effective cross-team collaboration with product and marketing divisions. One of the most exciting features of VSTS is powerful extensibility, with APIs offered in both major programming paradigms in use today -- JVM and .NET. The core organizational principle for full application lifecycle management is a single data construct -- the "work item" which documentation informs us "represents a thing," which can be anything that "a user can imagine." The power of work items comes through their extensible XML representation. Work items are combined into a Process Template, with such powerful Process Templates available as Agile, Scrum, and CMMI. VSTS will also allow us to analyze GHC Developer team performance with an integrated reporting data warehouse that uses a cube. Pricing for up to 100 users is $750 a month. Individual developers can also purchase subscriptions to Visual Studio Professional for $45 a month. I suggest we start directing resources towards a transition. I imagine all work to accomplish this could be done within a year, and by next April 1, the GHC development process will be almost unrecognizable from that today. Regards, Gershom

4 3

Re: [Haskell-cafe] Proposal: Professionalizing GHC Development
by David Banas 01 Apr '18

01 Apr '18

What a lovely idea! Might I suggest that, in making this change, we also adopt certain elements from both: - the Cult of Relevance, and - complex drama based managerial hierarchy, so as not to miss out on the wonderful benefits of those two features of modern hive mind development. So glad we’re finally ready to be brave in this new World, -db

1 0

ANN: hledger 1.9
by Simon Michael 01 Apr '18

01 Apr '18

I'm pleased to announce hledger 1.9. The version jump signals some noteworthy changes still landing (normal-positive reports, budget reporting) which are a kind of preview of 2.0. The next major release, on 2018/06/30, will be hledger 2.0. Thank you to release contributors: Eli Flanagan, Peter Simons, Christoph Nicolai, agander, M Parker, Moritz Kiefer, Mykola Orliuk. hledger (http://hledger.org) is a reliable, cross-platform program for tracking money, time or other commodities, using double-entry accounting and simple plain text file formats. It provides command-line, curses and web interfaces, and aims to be a pleasant and practical tool for personal, business or institutional use. What's new ? ------------ Some highlights: * the "financial statement" commands bs/bse/cf/is now show all normal balances as positive numbers, producing more conventional financial reports which are easier to share with others. (experimental) * bal/bs/bse/cf/is can now generate HTML reports * account codes can be used to customize account sorting * numbers in scientific E-notation are supported, eg in journal and CSV data * budget report improvements * general report cleanups More at http://hledger.org/release-notes#hledger-1.9 . Get started ----------- See http://hledger.org/download for all install methods. Often, to get the latest release you will need to build it. Here are some ways to do that: Using the hledger-install script, which requires only bash and will build and install the hledger tools in $HOME/.local/bin/. (Note: building haskell apps can take significant time, memory, and disk space, especially the first time. You can kill and restart the installer without losing progress. If it fails, please help us improve it by reporting the full output): $ curl -O https://raw.githubusercontent.com/simonmichael/hledger/master/hledger-insta… $ less hledger-install.sh # (do security review) $ bash hledger-install.sh # (add -v for more detail; use bash -x to show commands being run) Using hledger-install the more convenient, less secure way: $ curl https://raw.githubusercontent.com/simonmichael/hledger/master/hledger-insta… | bash Using stack: $ stack install hledger-lib-1.9 hledger-1.9 # hledger-ui-1.9 hledger-web-1.9 hledger-api-1.9 Using cabal: $ cabal update $ cabal install hledger-1.9 # hledger-ui-1.9 hledger-web-1.9 hledger-api-1.9 After installation, ensure $HOME/.local/bin is in your $PATH. Now try some commands: $ hledger -h # quick help $ hledger help # list built-in manuals $ hledger add # record some transactions $ hledger # list available commands Now perhaps work through the tutorial at http://hledger.org/step-by-step.html Or review the fine documents, presentations etc. at http://hledger.org and http://plaintextaccounting.org Or say hello and ask questions in the #hledger IRC channel on Freenode: http://irc.hledger.org New users and contributors are always welcome! Give feedback, report bugs, send pull requests, write about it, etc. And if you have been finding hledger useful, consider becoming a sponsor or donor to help to sustain and accelerate our progress (see home page). Our IRC channel is #hledger on Freenode (http://irc.hledger.org)

1 0