simln-lib/refactor: move parsing into its own module#231
Closed
f3r10 wants to merge 1 commit intobitcoin-dev-project:mainfrom
Closed
simln-lib/refactor: move parsing into its own module#231f3r10 wants to merge 1 commit intobitcoin-dev-project:mainfrom
f3r10 wants to merge 1 commit intobitcoin-dev-project:mainfrom
Conversation
Collaborator
Author
|
Hi, @carlaKC I found that async closures are already stabilized on the latest version of rust: rust-lang/rust#132706 so maybe I could update the CI to use version 1.85. WDYT? btw. most of the changes are based on this previous commit of yours: carlaKC@1951bb8 |
Contributor
|
WDYT of moving the NodeConnection enum into the parsing module as suggested in the issue description? |
Collaborator
Author
Contributor
Oh good news! I think let's bump version if we end up using them in the PR that addresses this? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix #214