You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To forward each "port" which can be any "network interface" implementation, hypervisor port and so on, trait objects are used (see RouterInput, `RouterOutput). This is kind of analogous to virtual function calls, which are not easily certified. A limited polymorphism for the possible port types would maybe be more applicable. But since the implementation for a "network interface" can come from another crate, defining a complete enum is difficult. Maybe we can use limited compile-time polymorphism to construct an enum for this? Is it possible to use a type in a653rs-router that is only known at compile-time at the use-site?
The text was updated successfully, but these errors were encountered:
To forward each "port" which can be any "network interface" implementation, hypervisor port and so on, trait objects are used (see
RouterInput
, `RouterOutput). This is kind of analogous to virtual function calls, which are not easily certified. A limited polymorphism for the possible port types would maybe be more applicable. But since the implementation for a "network interface" can come from another crate, defining a complete enum is difficult. Maybe we can use limited compile-time polymorphism to construct an enum for this? Is it possible to use a type in a653rs-router that is only known at compile-time at the use-site?The text was updated successfully, but these errors were encountered: