News for hackers. Stuff that matters.
Re:Async Rust Is A Bad Language by dgb23 on Friday September 08, 2023 @05:36PM (#37439734)
> I want to know if the function I'm calling is going to make a network request.

That has nothing to do with function coloring.

> Ideally I want to have the fundamental behavior of any function I call encoded in the function signature.

There is no distinction of async functions if you don't have function coloring that you can encode in type signatures.

Re:Async Rust Is A Bad Language by brigadier132 on Friday September 08, 2023 @05:48PM (#37439820)
> That has nothing to do with function coloring.

Sure, in the same way that types have nothing to do with enforcing logical correctness of software.

> There is no distinction of async functions if you don't have function coloring that you can encode in type signatures.

What are you trying to say with this statement?

Re:Async Rust Is A Bad Language by kprotty on Saturday September 09, 2023 @01:22PM (#37447757)
getaddrinfo() is a synchronous function that can do network requests to resolve DNS. The network property isn't reflected in its function signature becoming async. You can have an async_getaddrinfo() which does, but the former is just a practical example of network calls in particular being unrelated to function coloring.