-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
25 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Log 02: "Brainstorming & Understanding Procedural Macros" | ||
|
||
> 24 Oct 2024 | ||
## What I Worked On: | ||
|
||
- Brainstormed a new approach for | ||
[#3246](https://github.com/lightningdevkit/rust-lightning/pull/3246), shifting | ||
the responsibility for Blinded Path properties to `MessageRouter`. Because, | ||
"the Router must decide, a Blinded Path Type 🎶". | ||
- Took a first dive into | ||
[#3378](https://github.com/lightningdevkit/rust-lightning/pull/3378). | ||
Procedural macros are new territory for me, and I’m excited to explore them. | ||
|
||
## Reflections: | ||
|
||
Today reminded me that brainstorming and proper planning are the first half of a | ||
successful project. Figuring things out early has really set me up to tackle the | ||
problem head-on tomorrow! | ||
I also learned that proc macros are complex (xD), but they’re incredibly | ||
powerful. With the code introduced in | ||
[#3378](https://github.com/lightningdevkit/rust-lightning/pull/3378), we’ll | ||
avoid manually handling serialization/deserialization of outdated fields! | ||
Procedural macros feel like magic to me, and tomorrow I’ll try to unlock that | ||
magic for myself! 🪄 |