Skip to content

Conversation

aviatesk
Copy link
Member

I am writing a solution for #99 by overloading next_or_nothing!. This PR serves as a preparation for that, while the basic usage of LCU remains unchanged.

I am writing a solution for #99 by
overloading `next_or_nothing!`. This PR serves as a preparation for
that, while the basic usage of LCU remains unchanged.
@aviatesk aviatesk merged commit 54f6697 into master Sep 10, 2024
9 checks passed
@aviatesk aviatesk deleted the avi/recurse-next_or_nothing! branch September 10, 2024 09:20
aviatesk added a commit that referenced this pull request Sep 10, 2024
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.

1 participant