Jana Dönszelmann

Checks in the CI fail because all features are enabled in the CI, even on rust targets which do not yet support const generics. Disabling the `const-generics` feature for these...

Instructions globally are fine, but we need some part of it locally as well. For example, some of the code in the archive uses libraries (such as for Rust: generating...

Hi, I'm the maker of that crate :). The reason it uses ctor is because otherwise you can't really register some item in code against some other part of the...

ah, you just make some local state for every implementation. And you annotate the functions you want. Though It'd be awesome to see my library used in some larger project,...

I thought about this for a while (at first I was confused why there were no results) but after a while I started to really like it. The thing is,...

@yupferris I think I can get something like this to work:  It's very similar to what you say in your last comment I think

The generic S could also just be a non-generic struct (like Signal) but the current signal would not work because of all of the lifetime arguments. Module definitions would become...

The only thing I'm not sure about is the fact that previously you could name inputs and outputs. You can't really name type arguments. If we want to keep naming,...

I see. I haven't been too clear either. My comments specifically answer point 2: alternatives. I think it might be possible to make modules be structs which implements the a...

Working on this. Using MDBook + github pages (through Github CI). Going to frame it as a book in which the goal is to build a simple CPU using Kaze....