Andrea Giammarchi

FWIWI I've resolved the `peek()` case as such and it seems to work well: ```js class State extends Signal.State { peek() { return untrack(() => this.get()); } } ``` The...

@jods4 `untrack` is not about just one signal or computed, it's about running something potentially huge ... `peek()` as it is in Preact is for each single signal/computed and it's...

checking internals of the polyfill, it could indeed just return the internal symbol value and avoid extra stacks. Apologies I've misread your previous comment, I've thought you preferred `peek()` over...

@EisenbergEffect I feel like that's a stretch too far ... or better, I don't understand the use case for it, it feels surprise prone to me as "*a sneaky update...

agreed and on a second though, `untrack` is fine to exist and has tons of use cases already, `.peek()` is the "atomic untrack" within a state/computed and it's fine and...

@NullVoxPopuli > do we have a list of these? just the fact one can send errors or debug on Promise catch would be enough to me, as you never want...

my example was poorly presented ... I meant that whenever signals or computed are around and you want to: * serialize that value to send a JSON request to a...

my 2c: explicit `peek()` is intentional zero side-effects by design so I hope we can make it part of the specs ... `poke(value)` as suggested elsewhere as counter-method is undesired...

same here and it's not just about submodules, I'd say any folder that contains a `.git` one should have priority over the root folder (to be honest, even a way...

All your points could be addressed in here ... fancy filing a PR?