Kevin Herron

I'm not really sure about these changes. We didn't discuss this at any point, so I'm not sure why they're necessary at all. It's also odd that they are only...

I don't have time to materialize this from scratch right now, but if somebody else out there is going through the migration and wants to try to document the process...

Nice, thanks. You're probably one of very few people who are using all the stuff related to doing your own codegen. I think most users will have a much easier...

@peterfranciscook can you detail this a little more? > The async method (OpcUaClient::writeValuesAsync) in milo 1.x will quietly fail and does not return a failed future if you attempt this....

@peterfranciscook so what's the issue? Your test demonstrates the same thing mine does - the CompletableFuture _does_ complete (exceptionally), with the NPE reported in the nested exceptions. It _is_ expected...

> without breaking API compatibility before 2.0 If you're open to discussing Java API changes for 2.0 lmk via email. The non-idiomatic design of all the little Java data classes...

Reflection with `setAccessible` works for some of these. ``` val ctor = HeaderInfo::class.java.getDeclaredConstructor( Variation::class.java, QualifierCode::class.java, Boolean::class.java, Boolean::class.java ).also { it.trySetAccessible() } val headerInfo: HeaderInfo = ctor.newInstance(Variation.GROUP30_VAR1, QualifierCode.COUNT8, false, true) ```

Meh, not as bad as I thought yesterday. I'll just have to introduce some test helper functions: ```kotlin /** * Reflectively create a new [HeaderInfo]. */ fun newHeaderInfo( variation: Variation,...

In oo_bindgen there seems to be a distinction between classes and structs. All of the "struct" things could probably just have public constructors across the board without much concern for...

Not meaningfully, it only came up trying to write a unit test.