Proceedings of the 20th International Symposium on Principles and Practice of Declarative Programming 2018
DOI: 10.1145/3236950.3236952
|View full text |Cite
|
Sign up to set email alerts
|

Sequential and Parallel Improvements in a Concurrent Functional Programming Language

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3

Citation Types

0
4
0

Year Published

2019
2019
2021
2021

Publication Types

Select...
3

Relationship

3
0

Authors

Journals

citations
Cited by 3 publications
(4 citation statements)
references
References 27 publications
0
4
0
Order By: Relevance
“…Also other shared memory synchronization primitives like concurrent buffers and their encodability into λ (fut) are analyzed [24]. Other examples are the calculi CH [19] and CHF [14,15,21]. The latter is a program calculus that models the core of Concurrent Haskell [10]: it extends the functional programming language Haskell by concurrent threads and so-called MVars, which are synchronizing mutable memory locations.…”
Section: Introductionmentioning
confidence: 99%
“…Also other shared memory synchronization primitives like concurrent buffers and their encodability into λ (fut) are analyzed [24]. Other examples are the calculi CH [19] and CHF [14,15,21]. The latter is a program calculus that models the core of Concurrent Haskell [10]: it extends the functional programming language Haskell by concurrent threads and so-called MVars, which are synchronizing mutable memory locations.…”
Section: Introductionmentioning
confidence: 99%
“…Our goals are the comparison of programming languages, correctness of transformations, compilation and optimization of programs, in particular of concurrent programs. We already used the contextual semantics of concurrent (functional) programming languages to effectively verify correctness of transformations [16,23,24], also under the premise not to worsen the runtime [30]. We propose to test mayand should-convergence in the contextual semantics, since, in particular, it rules out transformations that transform an always successful process into a process that may run into an error, for example a deadlock.…”
Section: Introductionmentioning
confidence: 99%
“…In addition to the program executions, it is crucial to recognize (binding-)garbage and remove it, since we are interested in space improving transformations. It is shown in [11,12] that garbage collection and the modification of the standard reduction (i.e. program execution) leaves all interesting properties (equivalence of expressions, correctness of transformations) invariant, and thus this is a correct and space-optimizing transformation.…”
Section: Introductionmentioning
confidence: 99%
“…P 1 starts with a local peak, hence we keep in mind 14 as the sum of the first elements and replace P 1 by P 1 = [1,12,5,7,1]. The next step is to apply the pattern M 3 , which reduce it to P 1 = [1,12,1]. Thus the new problem is P 1 = [1, 12, 1], P 2 = [3, 11, 2, 10, 3],…”
mentioning
confidence: 99%