Skip to content

no warnings #137

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

Merged
merged 1 commit into from
Feb 14, 2023
Merged

no warnings #137

merged 1 commit into from
Feb 14, 2023

Conversation

zaucy
Copy link
Member

@zaucy zaucy commented Feb 11, 2023

No description provided.

@zaucy zaucy requested a review from Kelwan February 11, 2023 23:32
@zaucy
Copy link
Member Author

zaucy commented Feb 11, 2023

@Kelwan Could you check some of the warnings I fixed in the async reference? Make sure the unused lambda captures were accidentally left as opposed to a potential problem. Seems fine to me.

@zaucy zaucy merged commit d974559 into main Feb 14, 2023
@zaucy zaucy deleted the feat/no-warnings branch February 14, 2023 20:00
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

Successfully merging this pull request may close these issues.

2 participants