How are Carrier doing these days?

Josiah Noel josiahnoel at gmail.com
Tue Jun 6 14:54:32 UTC 2023


I guess one thing is that there isn't an easy way to mark a queue as
"closed" like golang channels. In Go an exception is thrown when we write a
value to a closed channel, and we can auto-stop iteration when the channel
is closed.

On Tue, Jun 6, 2023, 9:57 AM Olivier Peyrusse <kineolyan at protonmail.com>
wrote:

> Unfortunately no. I have been following that part from the distance. So
> far, I have use Loom on a prototype to replace a compute engine based on
> Counted Completer.
>
> I was wondering about Carrier as I remember it to be a sort of channel and
> was fishing for updates out of curiosity, as I was reading again books
> about Erlang as well as playing with Clojure Async and its channels.
>
> So, again, sorry for not being that helpful on the topic and thanks for
> any information
> Olivier
> ------- Original Message -------
> Le mardi 6 juin 2023 à 12:15, Alan Bateman <Alan.Bateman at oracle.com> a
> écrit :
>
> On 06/06/2023 10:03, Olivier Peyrusse wrote:
>
> Hello Loom devs,
>
> A long time ago on this mailing list, we read about Carrier classes, to
> implement stuff like message passing, Go channels, etc for the virtual
> threads of Loom.
> Unless I am mistaken, I have read anything  since 2020 about them [1] and
> [2].
> How is this project going? Is it still a construct you are looking at, but
> are currently focusing on polishing Virtual Threads for their general
> availability?
>
> One thing that is helpful to go with your question is to know if you've
> tried LinkedTransferQueue or any of the other blocking queues with virtual
> threads. Only asking because hearing feedback on using the existing APIs
> and hearing about any issues/limitations is always helpful.
>
> -Alan
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20230606/1670fdf7/attachment.htm>


More information about the loom-dev mailing list