tracked-tools/tracked-built-ins

You attempted to update `_value` on `TrackedStorageImpl`, but it had already been used previously in the same computation.

wagenet opened this issue · 2 comments

I suspect this isn't actually a bug, but any help that could be given to help me track this down would be greatly appreciated!

I figured it out. The message didn't help a ton though :)

Note that the message is an internal auto-tracking message, not specific to this library. The stack trace came from wherever you set during a read (normally: when setting tracked state during construction or in a getter), but it would be equally likely to happen in any construction of tracked state. Worth flagging up to think about whether and how we could make that error message better in Glimmer. If we could port back in some of the work @wycats has done on Starbeam debugging tools into the Glimmer auto-tracking system, that might be a good first step.