October 2018 - Haskell

PhD student positions in the Functional Programming group at Chalmers
by Mary Sheeran 19 Oct '18

19 Oct '18

Two PhD student positions in Functional Programming for guaranteed security in the Internet of Things The Octopi Project is led by Alejandro Russo, with Koen Claessen, John Hughes, Carl-Johan Seger and Mary Sheeran as PIs. We will develop new ways to program securely for the Internet of Things, working on everything from the programming model to hardware design. We have already appointed three doctoral students, and now we want to appoint two more, with emphasis on ways to express locality in computations and also on designing hardware for executing functional languages directly and efficiently. Carl-Johan Seger and Mary Sheeran will supervise the two new students, and they will join an amazing team. This is a real job with a decent salary for five years, and Gothenburg is a great place to live. The following link gives more details and it is through the link that you apply by pressing the button labelled Ansök. The deadline is October 31. http://www.chalmers.se/sv/om-chalmers/Arbeta-pa-Chalmers/lediga-tjanster/Si… Please consider applying, or advising your best students to apply. Mary Sheeran, Carl-Johan Seger and the Octopi team

1 0

Help inform GHC's development priorities
by Ben Gamari 18 Oct '18

18 Oct '18

tl;dr. Please a take a minute to express your thoughts on GHC's development priorities via this survey [1]. Hello everyone, The GHC developers want to ensure that we are working on problems that of most importance to you, the Haskell community. To this end we are surveying the community [1], asking how our users interact with GHC and which problems need to be addressed most urgently. We hope you will take a few minutes to give us your thoughts [1]. Thanks in advance for your time and, finally, thanks to the financial supporters that make our work GHC possible. Cheers, - Ben and the rest of the GHC developers [1] https://docs.google.com/forms/d/e/1FAIpQLSdh7sf2MqHoEmjt38r1cxCF-tV76OFCJqU…

1 0

Postdoc position on side-channel analysis and avoidance in Hardware (Chalmers University of Technology)
by Alejandro Russo 18 Oct '18

18 Oct '18

** Apologies for multiple copies ** --------------------------------------------------------------------------------- Postdoctoral position (up to two years) on side-channel analysis and avoidance in Hardware at Chalmers University of Technology, Sweden --------------------------------------------------------------------------------- * Important dates: October 30 - Deadline for applications November 5 - Tentative date for interviews * Expected starting date: January 2019. For details, including employment conditions and how to apply, see: <https://web103.reachmee.com/ext/I003/304/job?site=5&lang=UK&validator=a72ae…> This position is funded by a grant from Intel Corp and will get supervised by Prof. Carl-Johan Seger (<https://www.chalmers.se/en/Staff/Pages/secarl.aspx>) and Prof. Alejandro Russo (<http://www.cse.chalmers.se/~russo/>). Prof. Seger has, after 21 years at Intel corporation, a wealth of experience in verifying Intel's microprocessors and is intimately familiar with the constraints and scale of modern processors. He also has extensive experience in building formal verification tools, and symbolic simulators in particular, for modern microprocessors. Prof. Russo has vast expertise on protecting privacy in modern software systems and his work has impacted different research communities and appeared in prestigious conferences on programming languages, operating systems, and security. The project is dedicated to contribute and further research on (i) utilizing some notion of dependent types to verify security and the presence/absence of side-channels in multi-cycle circuits, (ii) apply symbolic execution techniques to boost accuracy when needed, (iii) implement a tool that combines these techniques, and (iv) perform evaluations on state-of-the-art public domain microprocessor designs. The position is to be carried out within both the Information Security (iSec) and Functional Programming (FP) research groups. Both groups combine world-class researchers in language-based security and functional programming. In addition, there is a strong type-theory research group that can be used as a source of knowledge in dependent types. Competitive candidates will have a strong computer science background, both theoretical and practical, with emphasis on programming languages techniques; expertise in some of the areas of interests for this position; a passion for high-quality software research and development; and excellent analytical and communication skills. Prior publications are meritorious. English is the working language for research in Chalmers's Department of Computer Science and Engineering. For a popular science description of the project, please refer to the following link: https://www.chalmers.se/en/departments/cse/news/Pages/Intel.aspx

1 0

FM'19: Call for Workshop & Tutorial Proposals
by Renato Neves 17 Oct '18

17 Oct '18

FM'19 - 3rd WORLD CONGRESS ON FORMAL METHODS PORTO, PORTUGAL, OCTOBER 7-11, 2019 formalmethods2019.inesctec.pt ---------------- CALL FOR WORKSHOP & TUTORIAL PROPOSALS --------------- ------------------------------------------------------------------------- Deadline for workshop & tutorial proposals: November 16, 2018 Notification of decision on workshops and tutorials: November 23, 2018 ------------------------------------------------------------------------- 1 ABOUT FM'19 ============= FM 2019 is the 23rd international symposium in a series organised by Formal Methods Europe (FME), an independent association whose aim is to stimulate the use of, and research on, formal methods for software development. Every ten years the symposium is organised as a World Congress. Twenty years after FM’99 in Toulouse, and ten years after FM’09 in Eindhoven, FM’19 is the 3rd World Congress on Formal Methods. Thus, FM’19 will be both an occasion to celebrate and a platform for enthusiastic researchers and practitioners from a diversity of backgrounds to exchange their ideas and share their experience. 2 PROPOSALS =========== For this major event, we are now inviting proposals for workshops, tutorials, or other satellite events that will complement the main FM Symposium and co-located conferences. The purpose of the satellite events is to provide an informal setting for participants to discuss technical issues, exchange research ideas, and to discuss and/or demonstrate applications. These may be driven by fundamental academic interests or by needs from specific application domains. We encourage a diversity of events relating to different varieties of formal models. Satellite events will take place on 7-8 October 2019. Satellite events would typically run for 1/2 or 1 day, but 2 day events will also be considered. The FM'19 organising committee aim to support one invited speaker per workshop. 3 SUBMISSION INFORMATION ======================== Researchers and practitioners wishing to organise a workshop or tutorial are invited to submit proposals by e-mail to the Workshops & Tutorials Chairs, Nelma Moreira (nam(a)dcc.fc.up.pt) and Emil Sekerinski (emil(a)mcmaster.ca) A proposal should not exceed three pages and should include the following information: * Title and brief technical description of the event, specifying the goals and the technical issues that will be its focus. * The names and contact information (web page, email address) of the organisers. In case of a workshop those will be the Programme Committee (PC) chairs and in this case a prospective list of international PC members is welcome. * Pointers to information about past editions of the event, if applicable. In case of a workshop, if it has taken place before; how often it has been colocated with FM? Which (other) conference(s) has the workshop been colocated with so far? Number of participants in the last instalment. * A discussion of the proposed format and agenda (for example paper presentations, tutorials, demo sessions, etc). * The proposed duration: half or one day. Exceptionally, two days events may be considered. * Potential invited speaker(s). * Procedures for selecting papers and participants and plans for the publication of proceedings, if any. * Tentative schedule for paper submission and notification of acceptance. The organisers of satellite events are expected to create and maintain a website for the event; handle paper selection, reviewing and acceptance; draw up a programme of talks; advertise their event though specialist mailing lists; prepare the informal pre-proceedings (if applicable) in a timely fashion; and arrange any post-proceedings. 4 IMPORTANT DATES ================= Submission of proposals: November 16, 2018 Notification of success of proposals: November 23, 2018 Notification of paper acceptance (if applicable): June 14, 2019 (limit date) FM'19 World Congress: October 7-11, 2019 Workshop/Tutorial dates: October 7-8, 2019 (also October 9-11 if space is an issue) Best Wishes, Nelma Moreira & Emil Sekerinski

1 0

Call for Workshops Proposals in conjunction with EDI40-2019
by Yazan Mualla 17 Oct '18

17 Oct '18

-------------------------------------------------------------------------- The 2nd International Conference on Emerging Data and Industry 4.0 (EDI40) Leuven, Belgium April 29 - May 2, 2019 http://cs-conferences.acadiau.ca/EDI40-19/ -------------------------------------------------------------------------- Important Date - Workshops Proposals Due: October 30, 2018 EDI40 2019 organizing committee invites proposals for workshops. The main objective of the workshops is to provide a forum for researchers and professionals to discuss a specific topic from the field of EDI40 and its related areas. ----------- Proceedings All papers accepted for workshops will be included in the EDI40 2019 proceedings, which will be published by Elsevier. The authors must follow Elsevier guidelines as given in EDI40 Website. The number of pages for workshop papers is limited to 6 pages. ----------- Proposal Format - Title of the workshop - Workshop Website: tentative address, or old address (if applicable) - Draft call for paper of the workshop - Tentative list of TPC members ----------- Workshops Chair - Dr.habil. Stéphane Galland, Université Bourgogne-Franche-Comté, Université de Technologie de Belfort-Montbéliard, France (Email: stephane.galland(a)utbm.fr)

1 0

Re: [Haskell] Treatment of unknown pragmas
by Matthew Pickering 16 Oct '18

16 Oct '18

I like the suggestion of a flag. For any realistic compilation you have to pass a large number of flags to GHC anyway. `stack`, `cabal` or so on can choose to pass the additional flag by default if they wish or make it more ergonomic to do so. On Tue, Oct 16, 2018 at 7:58 PM Jared Weakly <jweakly(a)pdx.edu> wrote: > > The main problem I see with this is now N tools need to implement support for that flag and it will need to be configured for every tool separately. If we standardize on a tool pragma in the compiler, all that stays automatic as it is now (a huge plus for tooling, which should as beginner friendly as possible). It also, in my eyes, helps enforce a cleaner distinction between pragmas as a feature-gate and pragmas as a compiler/tooling directive > > On Tue, Oct 16, 2018, 11:13 AM Vladislav Zavialov <vlad.z.4096(a)gmail.com> wrote: >> >> What about introducing -fno-warn-pragma=XXX? People who use HLint will add -fno-warn-pragma=HLINT to their build configuration. >> >> On Tue, Oct 16, 2018, 20:51 Ben Gamari <ben(a)smart-cactus.org> wrote: >>> >>> Hi everyone, >>> >>> Recently Neil Mitchell opened a pull request [1] proposing a single-line >>> change: Adding `{-# HLINT ... #-}` to the list of pragmas ignored by the >>> lexer. I'm a bit skeptical of this idea. Afterall, adding cases to the >>> lexer for every tool that wants a pragma seems quite unsustainable. >>> >>> On the other hand, a reasonable counter-argument could be made on the >>> basis of the Haskell Report, which specifically says that >>> implementations should ignore unrecognized pragmas. If GHC did this >>> (instead of warning, as it now does) then this wouldn't be a problem. >>> >>> Of course, silently ignoring mis-typed pragmas sounds terrible from a >>> usability perspective. For this reason I proposed that the following >>> happen: >>> >>> * The `{-# ... #-}` syntax be reserved in particular for compilers (it >>> largely already is; the Report defines it as "compiler pragma" >>> syntax). The next Report should also allow implementations to warn in >>> the case of unrecognized pragmas. >>> >>> * We introduce a "tool pragma" convention (perhaps even standardized in >>> the next Report). For this we can follow the model of Liquid Haskell: >>> `{-@ $TOOL_NAME ... @-}`. >>> >>> Does this sound sensible? >>> >>> Cheers, >>> >>> - Ben >>> >>> >>> [1] https://github.com/ghc/ghc/pull/204 >>> _______________________________________________ >>> ghc-devs mailing list >>> ghc-devs(a)haskell.org >>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs >> >> _______________________________________________ >> ghc-devs mailing list >> ghc-devs(a)haskell.org >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > > _______________________________________________ > ghc-devs mailing list > ghc-devs(a)haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

1 0

Treatment of unknown pragmas
by Ben Gamari 16 Oct '18

16 Oct '18

Hi everyone, Recently Neil Mitchell opened a pull request [1] proposing a single-line change: Adding `{-# HLINT ... #-}` to the list of pragmas ignored by the lexer. I'm a bit skeptical of this idea. Afterall, adding cases to the lexer for every tool that wants a pragma seems quite unsustainable. On the other hand, a reasonable counter-argument could be made on the basis of the Haskell Report, which specifically says that implementations should ignore unrecognized pragmas. If GHC did this (instead of warning, as it now does) then this wouldn't be a problem. Of course, silently ignoring mis-typed pragmas sounds terrible from a usability perspective. For this reason I proposed that the following happen: * The `{-# ... #-}` syntax be reserved in particular for compilers (it largely already is; the Report defines it as "compiler pragma" syntax). The next Report should also allow implementations to warn in the case of unrecognized pragmas. * We introduce a "tool pragma" convention (perhaps even standardized in the next Report). For this we can follow the model of Liquid Haskell: `{-@ $TOOL_NAME ... @-}`. Does this sound sensible? Cheers, - Ben [1] https://github.com/ghc/ghc/pull/204

2 1

Call for Workshops Proposals in conjunction with ANT-2019
by Yazan Mualla 16 Oct '18

16 Oct '18

========================================================================================== The 10th International Conference on Ambient Systems, Networks and Technologies (ANT-2019) Leuven, Belgium April 29 - May 2, 2019 http://cs-conferences.acadiau.ca/ant-19/ ========================================================================================== Important Date - Workshops Proposals Due: October 30, 2018 ANT-2019 organizing committee invites proposals for workshops. The main objective of the workshops is to provide a forum for researchers and professionals to discuss a specific topic from the field of ANT-2019 and its related areas. ------------ Proceedings All papers accepted for workshops will be included in the ANT-2019 proceedings, which will be published by Elsevier. The authors must follow Elsevier guidelines as given in ANT-2019 Website. The number of pages for workshop papers is limited to 6 pages. ------------ Proposal Format - Title of the workshop - Workshop Website: tentative address, or old address (if applicable) - Draft call for paper of the workshop - Tentative list of TPC members ------------ Workshops Chair - Dr.habil. Stéphane Galland, Université Bourgogne-Franche-Comté, Université de Technologie de Belfort-Montbéliard, France (Email: stephane.galland(a)utbm.fr)

1 0

ANN: DBFunctor – Functional Data Management / ETL Data Processing in Haskell
by Nikos Karagiannidis 16 Oct '18

16 Oct '18

Dear all, I am pleased to announce the release on Hackage of a new Haskell ETL Library, namely DBFunctor-0.1.0.0. (“ETL” stands for Extract Transform and Load and is the standard technology for accomplishing data management tasks in Data Warehouses / Data Marts and in general for data migrations, or for preparing data for any analytic purpose (Ad hoc queries, data exploration/data analysis, Reporting and Business Intelligence, feeding Machine Learning algorithms, etc.)) Version 0.1.0.0 can be used for **in-memory** data processing without the need of some external database. It is just a Haskell library linked in your Haskell program that enables full SQL functionality over tabular data (e.g., CSV files) but also the ability to write a full ETL data processing flow. Key features of this release are: 1. ** Julius DSL ** : A Type-Level Embedded Domain Specific Language (EDSL) for ETL 2. Supports all known relational algebra operations 3. Implements the ETL Mapping and other typical ETL constructs and operations 4. Applicable to all kinds of tabular data 5. In-memory, database-less data processing For more information please check out the project homepage: https://github.com/nkarag/haskell-DBFunctor Also there is a tutorial that can help you to easily get started with Julius DSL: https://github.com/nkarag/haskell-DBFunctor/blob/master/doc/JULIUS-TUTORIAL… * Learn how to implement your ETL flows with Julius DSL * Learn how to implement common ETL operations (e.g., append a delta to some target table, or create a surrogate key column etc.) * Build your own aggregate or analytic functions (e.g., string_agg, or a montlhy running total) * Express complex queries with Julius (equivalent to the WITH-clause in SQL) * and many more ... For any issues/problems with the DBFunctor package please open an issue on github. Happy data processing! Thank you. Best Regards, Nikos

1 0

ANN: DBFunctor – Functional Data Management / ETL Data Processing in Haskell
by Nikos Karagiannidis 15 Oct '18

15 Oct '18

Dear all, I am pleased to announce the release on Hackage of a new Haskell ETL Library, namely DBFunctor-0.1.0.0. (“ETL” stands for Extract Transform and Load and is the standard technology for accomplishing data management tasks in Data Warehouses / Data Marts and in general for data migrations, or for preparing data for any analytic purpose (Ad hoc queries, data exploration/data analysis, Reporting and Business Intelligence, feeding Machine Learning algorithms, etc.)) Version 0.1.0.0 can be used for *in-memory data processing* without the need of some external database. It is just a Haskell library linked in your Haskell program that enables full SQL functionality over tabular data (e.g., CSV files) but also the ability to write a full ETL data processing flow. Key features of this release are: 1. *Julius DSL*: A Type-Level Embedded Domain Specific Language (EDSL) for ETL 2. Supports all known relational algebra operations 3. Implements the ETL Mapping and other typical ETL constructs and operations 4. Applicable to all kinds of tabular data 5. In-memory, database-less data processing For more information please check out the project homepage: https://github.com/nkarag/haskell-DBFunctor Also there is a tutorial that can help you to easily get started with Julius DSL: https://github.com/nkarag/haskell-DBFunctor/blob/master/doc/JULIUS-TUTORIAL… * Learn how to implement your ETL flows with Julius DSL * Learn how to implement common ETL operations (append a delta to some target table, or create a surrogate key column etc.) * Build your own aggregate or analytic functions (string_agg, or a montlhy running total) * Express complex queries with Julius (equivalent to the WITH-clause in SQL) * and many more ... For any issues/problems with the DBFunctor package please open an issue on github. Happy data processing! Thank you. Best Regards, Nikos

1 0