From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: [ANN] Guile-Parallel 1.0.0 released
Date: Sat, 31 Dec 2022 19:58:09 +0000 [thread overview]
Message-ID: <f2cdfcc7-8d69-7fd3-5a65-0ff269c9eb4f@posteo.de> (raw)
In-Reply-To: <87wn68p6qi.fsf@laura>
Hello Olivier!
On 12/31/22 04:55, Olivier Dion via General Guile related discussions wrote:
> Hi Guilers,
>
> I'm happy to announce the first release of guile-parallel. A library
> that offers primitives for parallelization of your programs.
>
> Project page: <https://git.sr.ht/~old/guile-parallel>
>
> List of features:
>
> - Userspace threads (jobs schedulers)
>
> - Safe dynamic-wind for all types of threads (kernel and userspace)
>
> - sleep, usleep and nsleep for all types of threads
>
> - (ice-9 atomic) extensions, e.g. atomic counters
>
> - (ice-9 q) wrapper, i.e. safe for all types of threads
>
> - Barriers à la Pthread
>
> - Condition variables, mutexes and semaphores for kernel and userspace
> threads
>
> - Parallel vector-map vector-count, vector-sort, vector-map-reduce
>
> Next features:
>
> - Asynchronous I/O
>
> - Channels à la Go with a select syntax (maybe?)
>
> If there're interests, usages or requests for it, please let me know! I
> might add it to Guix if some find it useful.
>
> Regards,
> old
I looked at the examples in the repository a bit and it looks impressive!
Maybe I can already make use of it in coming AoC puzzles.
I am currently a bit confused about where the line is between a good use-case
for guile-parallel and guile-fibers. Or whether they could work well together or
the people making them should work together ; )
Regards,
Zelphir
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2022-12-31 19:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 3:55 [ANN] Guile-Parallel 1.0.0 released Olivier Dion via General Guile related discussions
2022-12-31 9:06 ` Damien Mattei
2022-12-31 19:58 ` Zelphir Kaltstahl [this message]
2022-12-31 20:31 ` Olivier Dion via General Guile related discussions
2023-01-02 16:13 ` Greg Troxel
2023-01-02 17:59 ` Maxime Devos
2023-01-02 20:45 ` Greg Troxel
2023-01-02 21:24 ` Olivier Dion via General Guile related discussions
2023-01-02 23:56 ` Olivier Dion via General Guile related discussions
2023-01-03 10:57 ` Damien Mattei
2023-01-03 21:40 ` guile-fibers timerfd_create bug (was: Re: [ANN] Guile-Parallel 1.0.0 released) Maxime Devos
2023-01-03 22:38 ` Damien Mattei
2023-01-03 22:43 ` Maxime Devos
2023-01-04 1:28 ` Olivier Dion via General Guile related discussions
2023-01-03 22:06 ` [ANN] Guile-Parallel 1.0.0 released Olivier Dion via General Guile related discussions
2023-01-03 22:29 ` Damien Mattei
2023-01-02 20:28 ` Olivier Dion via General Guile related discussions
2023-01-08 13:30 ` Zelphir Kaltstahl
2023-01-08 14:44 ` Olivier Dion via General Guile related discussions
2023-01-08 15:17 ` Zelphir Kaltstahl
2023-01-08 15:55 ` Olivier Dion via General Guile related discussions
2023-01-08 15:59 ` Zelphir Kaltstahl
-- strict thread matches above, loose matches on Subject: below --
2023-01-03 16:47 dsmich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f2cdfcc7-8d69-7fd3-5a65-0ff269c9eb4f@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@gnu.org \
--cc=olivier.dion@polymtl.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).