Alex Rickabaugh

Watchers are by definition owned things - something has to destroy them, otherwise they'll keep notifying. It's similar to registering an event listener on the `window`. It'd be unusual, but...

Having watchers that automatically shut down when they go out of scope feels very unpredictable and error-prone to me. Consider all of the warnings on [`FinalizationRegistry`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry#avoid_where_possible) about the lack of...

> Should a watcher strongly retain its sources? At least with "correct" usage, I think watchers will never have the only remaining reference to a source, because in order to...

@shaylew ahhh, yeah, I was talking about a dependency that was upstream of a watched `Computed`. I see what you mean - if you watch a `Signal.State` and every other...

This PR was merged into the repository by commit b400e2e4d4c27a9c8d8e91b52852ef7b64f7591a.

This PR was merged into the repository by commit 7b0777b3040d4392e1efd1120bac605c376edc6e.

Reopening as this is a separate issue than #55808.

This is a duplicate of #55166 which has the previous discussion (which concluded that `model()` should not support `transform`).

I'm going to steal this issue and refocus it a bit. `transform` support isn't necessary to address the problem you're talking about. If we had a way to declare that...

> But how would you transform the string to the number for input values? At the end the component internally only want number and will always emit number. Only the...