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
Instead of calling the module into which Rust types are emitted
'<skeleton>_types' just call it 'types'. There isn't really a good
reason for the former naming from what I can tell. Client code will
always be able to prevent naming conflicts, because it is free to
include the generated skeleton inside its own module. In fact, that's
what all our examples do:
> mod capable {
> include!(concat!(
> env!("CARGO_MANIFEST_DIR"),
> "/src/bpf/capable.skel.rs"
> ));
> }
> use capable::capable_types::uniqueness;
In the above snippet, the usage of capable::capable_types is a needless
repetition.
Signed-off-by: Daniel Müller <[email protected]>
0 commit comments