Bradley Harden

> Alternatively, a version of pyVHDLModel might be implemented in Rust, but I guess that's duplicating the effort. @umarcor, isn't pyVHDLModel basically just a VHDL AST in Python? rust_hdl already...

@LarsAsplund, I don't want to get too sidetracked responding to your question, but I'll try to explain a little bit. In my case, I think there are a few different...

@umarcor and @LarsAsplund, I haven't had a ton of time to work on this, but I have made _some_ progress recently. I've done a bit more prototyping, and I've encountered...

@umarcor, yes, I realized in my sleep that I had misunderstood. I didn't fully understand the `eid` parameter. I re-read the code, and I think I follow everything now. However,...

@umarcor, thanks for the example in both VHDL and C. It was very helpful to understand how you intended the interface to work. Also, thanks for taking the time to...

@umarcor, sorry for the delay. I haven't had much free time lately. I wanted to go through your examples in more detail before responding, but I don't know how long...

Minor addition, but I think there should also be functions to retrieve the actor, logger, etc. from the VC. Should they be named `actor`, `logger`, etc. or `as_actor`, `get_logger`, etc.?

> The second step would be to define an element_t, As you noted the unconstrained string would be problematic with VHDL-93 but does it really help to have a record...

Also, you didn't answer one of my Gitter questions. Some of my changes to `codec_pkg` and `codec_builder_pkg` broke the code generation tools for the old `com` library. Is that ok?...

@LarsAsplund, I remembered the issue that motivated my distinction between `element_t` and `element_ptr_t`. I think it would be elegant and unifying to use some version of `element_t` as the fundamental...