Dynamic cache-key with side effects does not work

[somebee]

<div@{i++}> ends up incrementing the counter twice.

[madmaniak]

What's the use case for dynamic cache-key?

[somebee]

It is useful when you want to render tags that should be cached but are not inside or named tags. Here is a very short (and clumsy) explanation at scrimba.com - What is the use-case for dynamic cache-keys? :)

[madmaniak]

Oh sorry, this part I know - I was just wondering what's this construct for {i++}?
But despite that, this looks awesome 🙀 I've learnt I don't need render and self at the and of build anymore. Probably looking for {object:id} by default if exist would be too much and hit performance. What do you think?