John Baublitz

@ollipa Given that this is somewhat unrelated to the builder pattern and more related to the visibility of struct fields after the builder has been used to build those structs,...

Hi @Alexandero89! Your use of `u16` and then conversion to the correct type after matching on `MYCMDS` is generally the way to do it. It is hard to come up...

Okay, I think I see what you're missing now. So the current way to do this is to get the field `nla_type` and parse the `u16` as `ATTRIBUTES_COMMAND_ONE` or `ATTRIBUTES_COMMAND_TWO`...

Pushing this back 0.7.0.

Work started in branch `v0.5.0-dev`.

@isomer I'm sorry I never replied to this! I'm probably going to target this for 0.8.0 because as you can see from #182, there's already so much going into 0.7.0.

> Since you asked for opinions: > > 1. If neli::{NlSocket,NlSocketHandle} share a function in common with neli::tokio::NlSocket, they should ideally have the same function signature and do the same...

@ollipa Do you mind if I add you to assignees here just to keep track of the fact that we're working on this together?

See PR #93 for a more in depth discussion.

Hi @isomer! I've seen this capability described in the kernel code before but hadn't dug into it too much. This seems like it could absolutely be valuable! What I'm mostly...