D and Async I/O

Sebastiaan Koppe mail at skoppe.eu
Tue May 12 09:57:51 UTC 2020


On Tuesday, 12 May 2020 at 09:23:40 UTC, Russel Winder wrote:
> On Mon, 2020-05-11 at 19:34 +0200, Jacob Carlborg via 
> Digitalmars-d-learn wrote:
>> On 2020-05-11 16:44, Russel Winder wrote:
>> 
>> > Crickey, a third option. This wil increase my dithering! ;-)
>> 
>> Forth: Mecca [1] :)
>> 
>> [1] https://github.com/weka-io/mecca
>
> Hummm… it seems everyone who needed async activity and 
> particularly I/O in D has written their own. Mostly along with 
> all their own data structures and algorithms library.

Yeah it is a shame, but you see it in almost every language. 
Probably means concurrency and io isn't a fully solved problem 
yet.

> I keep trying to come back to D for GTK+ working, but in the 
> end I keep going back to Python and Rust because D has no 
> futures, and no added extras over GtkD auto translation of the 
> GTK+ API to make it D-y in the way gtk-rs make GTK+ Rust-y.
>
> Sorry for the apparent gloom, I just felt the need to tell it 
> how I feel.

I think there are a lot of lessons to be learned from all the 
efforts in the programming community.

We should:

- get stackless coroutines
- get structured concurrency
- steal as many idea from the C++'s executors proposal 
(http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p0443r13.html)


More information about the Digitalmars-d-learn mailing list