On the proliferation of try (and, soon, await)

• swift-evolution

  124 15,003 9.7 Markdown

  This maintains proposals for changes and user-visible enhancements to the Swift Programming Language.

  

Indeed, async let seems like a massive improvement! (Judging by this proposal [1].) Still the wrong default IMO (should be `let x = async ...` so that you can then do `let xs = [async f(), async g()]`) but definitely a step in the right direction.

Now just remove `async` and `throws` function annotations and/or make those default, and all noise will be removed!

[1] https://github.com/apple/swift-evolution/blob/main/proposals...

• csharplang

  262 10,868 9.6 C#

  The official repo for the design of the C# programming language

  

> it captures the current SynchronizationContext by default.

Which results in the majority of async code, which doesn't run in a UI context, needing to spam `.ConfigureAwait(false)` everywhere. It's the most visible wart in C# today - and no end of requests for a more succint alternative: https://github.com/dotnet/csharplang/discussions/645

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project