Kristian Larsson

I'm leaning towards not using libnetconf2 since it seems like we are loosing quite a bit of control in the low level socketry. The netconf part should be fairly minimal...

Closing, there is now a native netconf client https://github.com/orchestron-orchestrator/netconf - or at least an embryo of one, it does the basics.

@nordlander just to be clear, in Jai, `:=` is variable (re)assignment, like many other languages. It is `::` that defines a constant. My spontaneous suggestions wasn't particularly thought through, perhaps...

I attempted this and realized that we currently don't run the Env init function - it is entirely constructed from C code, so adding that part ``` actor Env(...): stdio...

I think we need #2368 for this and since we haven't even designed how #2368 will work, that might take some time. Until further, deferring this till next year.

Not sure that it "must" be coupled... like, if you turned on exhaustive-patterns on the above, it would essentially force you to write an `case _: ...` I guess!? So...

An alternative to named tuples is to use a class QName (other XML libs call it QName), but namedtuples seem simpler and thus more appealing. Another variant for the structure...

I'm going to close this. I think it's pretty clear that we are violating the intention for how Zig was to be used and it's just a world of pain...

I attempted this and realized that we currently don't run the Env init function - it is entirely constructed from C code, so adding that part ``` actor Env(...): stdio...

I think we need #2368 for this and since we haven't even designed how #2368 will work, that might take some time. Until further, deferring this till next year.