@commonsguy Super interesting scenario with the remember not working as expected. In a way, and obviously only after I know the solution, it kinda makes sense that since you call the content lambda from two completely separate call sites it is treated as two separate compostables. While in the "solved" approach it's all in the same line.

But I can't say I can, with any confidence, answer why exactly that is and how the compiler is making that decision.

Thanks for sharing it!