Remove all the easily removed Nop messages that some of the web components have.
I was under the misapprehension that Callback<T> had to return a message due to my learning yew without enough Rust knowledge to see that it's only ones created by a Scope that have that requirement. Since a Scope can be cheaply cloned, it makes sense to just change the Callbacks that return Nop to include a Scope that they can send messages to when there's a message to send. When there's no message to send, do nothing.
This is just something I noticed as I was DRYing the event_row.rs code (#1451). It's no big deal, but it's a perfect little chore to do when I have a small block of time to kill and don't want to bite into something bigger. OTOH, being my mom's minder is significantly fragmenting my time and finding "perfect little chores" may be preventing me from finding a better way to deal with that fragmentation. !Whee
Remove all the easily removed
Nop
messages that some of the web components have.I was under the misapprehension that
Callback<T>
had to return a message due to my learningyew
without enough Rust knowledge to see that it's only ones created by aScope
that have that requirement. Since aScope
can be cheaply cloned, it makes sense to just change theCallback
s that returnNop
to include aScope
that they can send messages to when there's a message to send. When there's no message to send, do nothing.This is just something I noticed as I was
DRY
ing the event_row.rs code (#1451). It's no big deal, but it's a perfect little chore to do when I have a small block of time to kill and don't want to bite into something bigger. OTOH, being my mom's minder is significantly fragmenting my time and finding "perfect little chores" may be preventing me from finding a better way to deal with that fragmentation. !Whee