Rusty Russell c71e16f784 broadcast: invert ownership of messages. ... Make the update/announce messages own the element in the broadcast map not the other way around. Then we keep a pointer to the message, and when we free it (eg. channel closed, update replaces it), it gets freed from the broadcast map automatically. The result is much nicer! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>		2018-05-10 21:35:53 +02:00
..
.gitignore	gossipd/test/run-bench-find_route: don't abort if we try to route to ourselves	2017-12-20 13:57:28 +01:00
Makefile	gossipd: Check features in node_announcement and channel_announcement.	2018-01-13 11:29:42 +01:00
run-bench-find_route.c	broadcast: invert ownership of messages.	2018-05-10 21:35:53 +02:00
run-find_route-specific.c	broadcast: invert ownership of messages.	2018-05-10 21:35:53 +02:00
run-find_route.c	broadcast: invert ownership of messages.	2018-05-10 21:35:53 +02:00
run-initiator-success.c	gossipd/lightningd: use wireaddr_internal.	2018-05-07 22:37:28 +02:00
run-responder-success.c	gossipd/lightningd: use wireaddr_internal.	2018-05-07 22:37:28 +02:00