In general, though, we can’t solve this problem with pull-only reactivity. The input node that gets updated just doesn’t have the information to tell us what its dependants are, and therefore what output nodes are eventually going to need to change. But we could try a different approach, where we do try and store that information. A combination of pushing and pulling — some kind of suicide squad push-pull reactivity?
Warning: Narrowing conversions can lose data. Casting a large int to i8 will wrap on overflow — no runtime error, just silent truncation.
，更多细节参见新收录的资料
Жители Санкт-Петербурга устроили «крысогон»17:52，更多细节参见新收录的资料
$ be post //replicated.live/@gritzko/librdx