Using syscall.RtMsg on Linux

[7sunarni]

I think we don't need to define struct routeInfoInMemory because there is already defined struct sycall.RtMsg in Golang standard library

[7sunarni]

@willscott

[willscott]

I think this would mean the library couldn't be used on arm devices, right? - I see RtMsg in the arm64 types, but it isn't there for the arm definitions that would be used for e.g. older raspberry pi's / other armv6/armv7 chips.

I appreciate the simplification - are there other benefits to consider in whether it's worth using the partial upstream definition?

[7sunarni]

I think this would mean the library couldn't be used on arm devices, right? - I see RtMsg in the arm64 types, but it isn't there for the arm definitions that would be used for e.g. older raspberry pi's / other armv6/armv7 chips.

I think you may miss something. There is also RtMsg definition in arm. So i think it could run in other arm chips.

are there other benefits to consider in whether it's worth using the partial upstream definition?

Temporary no.

[willscott]

you're right! my search missed the arm one. this seems unobjectionable 👍