Skip to content

Conversation

@pm47
Copy link
Member

@pm47 pm47 commented Apr 24, 2020

It was error-prone (cf bff833b) and not a good practice according to @sstone.

Commit 2ad91b2 is optional, let me know what you think.

@pm47 pm47 requested a review from t-bast April 24, 2020 13:43
@pm47 pm47 force-pushed the revert-use-sender branch from fbf38c8 to 2ad91b2 Compare April 24, 2020 13:45
@t-bast
Copy link
Member

t-bast commented Apr 24, 2020

I like the revert, but not sure about 2ad91b2
While it simplifies a bit the code, PeerRoutingMessages are not necessarily gossip, so if we want to make those evolve independently (add new fields) we'll likely need to revert that.
Not a strong NACK, but not a strong ACK either :)

@pm47
Copy link
Member Author

pm47 commented Apr 24, 2020

I like the revert, but not sure about 2ad91b2
While it simplifies a bit the code, PeerRoutingMessages are not necessarily gossip, so if we want to make those evolve independently (add new fields) we'll likely need to revert that.
Not a strong NACK, but not a strong ACK either :)

I reverted with 13ea541 (insert 'yo_dawg.jpg') but kept the LightningMessage->RoutingMessage signature change.

@pm47 pm47 merged commit 9c748e4 into master Apr 24, 2020
@pm47 pm47 deleted the revert-use-sender branch April 24, 2020 14:54
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.

3 participants