Alex Rickabaugh

I'd rather have specific issues for specific conditions, since how addressable they are varies widely. I'm going to close this issue actually, as the basic type-checking mode (`fullTemplateTypeCheck: false`) has...

Closing as Elements and Ivy do work together :)

This was resolved a while back. The error message now correctly indicates the variable declaration and where the template is attempting to set it.

I'm going to close this issue as a duplicate of #15280 - fundamentally this is a request for template local variables.

@AndrewKushnir I'm thinking that even if we can't change the main behavior, there are two things which we should consider: 1. We should consider the interaction with `nonNullable: true`. Perhaps...

Yep, by (2) I mean doing `new FormControl(undefined, {nonNullable: true})` would be an error - we'd force you to go through the `new FormControl({value: undefined, ...}, ...)` signature instead.

@diesieben07 hahaha! I took a look at elements this afternoon and encountered literally all of the problems you called out. I wish I'd read your comment beforehand, it would've saved...

It's worth thinking about whether `introspectSources` should dedup automatically or not. I could see a perf argument that it's better to leave deduplication up to the consumer in the case...

Ahh, `watch` definitely should (in the sense that you should ideally get one notification per signal being watched).

@fabiospampinato mentions that zero-arg functions are effectively uncached computeds. Because dependency tracking is contextual, it doesn't matter whether there's extra stack frames in between the consumer (current reactive context) and...