Dion Dokter

^^^ @alexmoon Your first point is now fixed too. This can cause errors in the generated code now which is not ideal. I'd like to catch it in the macro...

> Overall I think the new DSL is a definite improvement. The error checking is great and not having to repeat things like byte order and address type over and...

Ok, you've convinced me. It now has the chiptool interface. Also there are now two constructors for the default value and the zero value. I think I might be able...

Alright fine. I've implemented reset value overrides on register refs. The RegisterOperation now takes a function pointer to the correct constructor. I was worried this would be bad, but the...

Alright, got caught again by assuming names are unique. I've now added a proper unique ID type so hopefully that won't happen again. I've also bulked up the cfg processing...

Ok, let's just merge it. More testing needed though!

Ok I'm gonna pause this effort. I've now spent many hours on this. You'd think having to deal with all the different register types would be the problem. But no....

@enbyted hi, interesting problem. I'm open to ideas on fixing it. That said, the function is only really meant for debugging purposes. So if it doesn't quite work for everyone,...

Ok, well... Not much I can do then. I see your problem. The only other suggestion I can make is that you do make the interface blocking, but also expose...

Interesting feature I hadn't considered yet: Some people will want one transaction where both writes and reads happen. `Multi([write(foo), read(bar)])` This is even crazier to support...