Jake Taylor

I actually did a quick test of this for `sim::ir::Expr::write`, and ended up with an ICE, so I backed out - this should be properly isolated/reported when I have more...

Note that a Rust feature I was unaware of until now is `track_caller`, which might be useful for providing better error messages by providing information about the calling function. A...

Indeed, the usage of the library is much more like using a compiler (that you bootstrap yourself via `build.rs` usually) than a typical library.

Thanks for bringing this to my attention! Indeed this looks like an interesting project, and seeing as the [reference impl](https://github.com/fabianschuiki/llhd) appears to be in Rust, I think making a backend...

I just realized, considering moving signal bit widths into the type system (#13), it fits really nicely with the proposed `Input` and `Output` types, because their widths would be explicitly...

Thanks for the feedback. I have to be honest, though - I have no idea what you're talking about/suggesting, or how to interpret your feedback! It may not have been...

Apologies for not writing back about this until now, but I've struggled to be able to make time to internalize what you've written and respond properly while prioritizing IRL things...

Also, just to have an example built with what I currently have, here's [an LFSR](https://github.com/xenowing/xenowing/blob/master/rtl/src/mimas_a7/test/lfsr.rs): ```rust use kaze::*; pub struct Lfsr Lfsr { let m = p.module(instance_name, "Lfsr"); let shift_enable...

That sounds good, but I'd appreciate it if you waited until #23 is addressed. I've been putzing on it for a couple months on [this branch](https://github.com/yupferris/kaze/tree/the-great-module-instance-collapse) along with a [matching...

Also, bear in mind that my response capacity is somewhat limited these days; I've recently had a child and changed jobs, and the dust is still settling.