Stream: wg-async-foundations

Topic: the issue of audience


Naveed Pasha (Mar 10 2019 at 09:29, on Zulip):

Hello all,
I went through the async-await status report on the "this week in Rust" section and would like to contribute to the issue of audience

# whoami
- My experience level: 1/100 (I started learning Rust last month because I'm not hard core enough to take the world of C/C++ )
- My use case: free, open-source implementation of the IEEE 11073 standard for communication to and between medical devices
- My need for async-wait: medical management is primarily event driven; data generated by one device will async trigger events on another device or on the medical record and needs to await their response to proceed appropriately

# my answer
Audience should be (~and I hate to say this~) early adopters

# my justification
This feature is to important to release to the masses all at once since any and all bugs may
1. put off users
2. set in motion a chain of bad programming habits that may propagate through time

# how to implement in nightlies
As a async!() macro with { await } statements in the body as this will make it easier (~I think~) for debugging with println!() and/or eprintln!() macros. Later, when the feature is truly mature, it could be moved to a proper keyword in the Rust syntax

nikomatsakis (Mar 11 2019 at 19:31, on Zulip):

thanks for the feedback, @Naveed Pasha =)

nikomatsakis (Mar 11 2019 at 19:32, on Zulip):

As an aside, I'd generally prefer to keep this Zulip focused on impl questions rather than policy, but I appreciated the careful way you wrote up your perspective (and where you are coming from)

Last update: Nov 18 2019 at 02:10UTC