Saving a Third of Our Memory by Re-Ordering Go Struct Fields (2020)

Re:Saving a Third of Our Memory by Re-Ordering Go Struct Fie... by Joker_vD on Monday January 10, 2022 @06:19AM (#29873136)

Huh. So it's basically undocumented w.r.t. the actual implementation details, I was mostly interested in how they manage to bolt interfaces onto structs when they're separately compiled: e.g. if libFoo.so has "struct Foo {}" and "func (x Foo) Frob() { ... }" in it, and if libFrob.so has "interface Frobber { func Frob() }", and then they're linked together to the main application, will Foo actually implement Frobber? If yes, how?

[ Parent | on HN ]

Re:Saving a Third of Our Memory by Re-Ordering Go Struct Fie... by pjmlp on Monday January 10, 2022 @01:33PM (#29879273)

I guess that is the whole point of not having a stable ABI, you also won't find much documentation how C++ compilers do it, beyond reading the code.

[ Parent | on HN ]