Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: find some different mechanism for generic router ports #8

Open
dadada opened this issue Apr 10, 2024 · 1 comment
Open

feat: find some different mechanism for generic router ports #8

dadada opened this issue Apr 10, 2024 · 1 comment

Comments

@dadada
Copy link
Collaborator

dadada commented Apr 10, 2024

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?

@dadada
Copy link
Collaborator Author

dadada commented Nov 11, 2024

Would need to merge the platform-specific crates into one and use features

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant