Originally posted by bug77
View Post
Announcement
Collapse
No announcement yet.
Rust 1.39 Released With Async-Await Support, Attributes On Function Parameters
Collapse
X
-
Guest replied
-
That's a lot of good news! I tried Rust when in was in beta, and that was painful but cool (I feel weird to say that), should give Rust another try now. Just need a project excuse to code in Rust
Leave a comment:
-
Originally posted by kpedersen View PostIt was only invented and became popular because of the limitations of web browser environments. If Javascript interpreters were correctly multithreaded from the start and didn't freeze the browser on a tightloop, callbacks calling callbacks calling callbacks would remain a niche clusterfsck left entirely to amateurs.
- Likes 3
Leave a comment:
-
Originally posted by DoMiNeLa10 View PostAsync await is pure cancer no matter the language. It makes code convoluting, error handling becomes flimsy and cumbersome. Implementing a proper monadic interface is the way to go.
- Likes 1
Leave a comment:
-
Originally posted by DoMiNeLa10 View PostAsync await is pure cancer no matter the language.
Personally, I am a big fan of an explicit actor/state/event model - but that can be cumbersome to implement in most languages. I should probably seriously learn Erlang one day
- Likes 1
Leave a comment:
-
Originally posted by DoMiNeLa10 View PostAsync await is pure cancer no matter the language. It makes code convoluting, error handling becomes flimsy and cumbersome. Implementing a proper monadic interface is the way to go.
I'll also take async/await over callback style any day
- Likes 1
Leave a comment:
-
Having easily implemented a new feature for hyper 0.13 with async-await being available and then struggling for a couple of days to backport it to 0.12 without async-await, I very much welcome this.
- Likes 1
Leave a comment:
-
Originally posted by DoMiNeLa10 View PostAsync await is pure cancer no matter the language. It makes code convoluting, error handling becomes flimsy and cumbersome. Implementing a proper monadic interface is the way to go.
It was only invented and became popular because of the limitations of web browser environments. If Javascript interpreters were correctly multithreaded from the start and didn't freeze the browser on a tightloop, callbacks calling callbacks calling callbacks would remain a niche clusterfsck left entirely to amateurs.
- Likes 2
Leave a comment:
-
Guest repliedAsync await is pure cancer no matter the language. It makes code convoluting, error handling becomes flimsy and cumbersome. Implementing a proper monadic interface is the way to go.
- Likes 4
Leave a comment:
-
This is absolutely awesome. Probably the most awaited (pun intended) feature in years.
- Likes 5
Leave a comment:
Leave a comment: