wip: enable more diffing

packages/core/src/events.rs

@@ -10,14 +10,62 @@ use crate::{innerlude::ScopeIdx, virtual_dom::RealDomNode};
 
 #[derive(Debug)]
 pub struct EventTrigger {
+    ///
     pub component_id: ScopeIdx,
+
+    ///
     pub real_node_id: RealDomNode,
+
+    ///
     pub event: VirtualEvent,
+
+    ///
+    pub priority: EventPriority,
+}
+
+/// Priority of Event Triggers.
+///
+/// Internally, Dioxus will abort work that's taking too long if new, more important, work arrives. Unlike React, Dioxus
+/// won't be afraid to pause work or flush changes to the RealDOM. This is called "cooperative scheduling". Some Renderers
+/// implement this form of scheduling internally, however Dioxus will perform its own scheduling as well.
+///
+/// The ultimate goal of the scheduler is to manage latency of changes, prioritizing "flashier" changes over "subtler" changes.
+#[derive(Debug)]
+pub enum EventPriority {
+    /// "Immediate" work will interrupt whatever work is currently being done and force its way through. This type of work
+    /// is typically reserved for small changes to single elements.
+    ///
+    /// The primary user of the "Immediate" priority is the `Signal` API which performs surgical mutations to the DOM.
+    Immediate,
+
+    /// "High Priority" work will not interrupt other high priority work, but will interrupt long medium and low priority work.
+    ///
+    ///
+    /// This is typically reserved for things like user interaction.
+    High,
+
+    /// "Medium priority" work is generated by page events not triggered by the user. These types of events are less important
+    /// than "High Priority" events and will take presedence over low priority events.
+    ///
+    /// This is typically reserved for VirtualEvents that are not related to keyboard or mouse input.
+    Medium,
+
+    /// "Low Priority" work will always be pre-empted unless the work is significantly delayed, in which case it will be
+    /// advanced to the front of the work queue until completed.
+    ///
+    /// The primary user of Low Priority work is the asynchronous work system (suspense).
+    Low,
 }
 
 impl EventTrigger {
-    pub fn new(event: VirtualEvent, scope: ScopeIdx, mounted_dom_id: RealDomNode) -> Self {
+    pub fn new(
+        event: VirtualEvent,
+        scope: ScopeIdx,
+        mounted_dom_id: RealDomNode,
+        priority: EventPriority,
+    ) -> Self {
         Self {
+            priority,
             component_id: scope,
             real_node_id: mounted_dom_id,
             event,
@@ -78,7 +126,7 @@ pub mod on {
         ( $( $eventdata:ident($wrapper:ident): [ $( $name:ident )* ]; )* ) => {
             $(
                 #[derive(Debug)]
-                pub struct $wrapper(Rc<dyn $eventdata>);
+                pub struct $wrapper(pub Rc<dyn $eventdata>);
                 impl Deref for $wrapper {
                     type Target = Rc<dyn $eventdata>;
                     fn deref(&self) -> &Self::Target {