Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: always use return await instead of return #684

Open
Tracked by #675
KnorpelSenf opened this issue Dec 15, 2024 · 0 comments
Open
Tracked by #675

refactor: always use return await instead of return #684

KnorpelSenf opened this issue Dec 15, 2024 · 0 comments

Comments

@KnorpelSenf
Copy link
Member

This will improve stack traces, but add extra spins to the event loop. We have to bench this and then decide whether to move forward with it. If this is a noticeable bottleneck (hot path of the lib) then we should prevent this from happening.

@KnorpelSenf KnorpelSenf mentioned this issue Dec 15, 2024
48 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant