Schuyler Eldridge

Thanks for writing this up and providing concrete use cases. This was discussed at the dev meeting today. There's no conclusion, yet, but people are amenable to either (in serialized...

I keep meaning to loop back to this issue. We've fixed all of this except for `flip`. Note that fixing this is from the perspective of simplifying parsing and not...

Auto-port punching is totally useful as a Chisel API across a non-separately compiled boundary. I'm not arguing against this in any way. We should support an auto-port punching API like...

I fixed the missing comma issue in d169da3adea4686bee4287357c109820d2116ec0. I believe this existed in the spec only to work around long-line issues. However, it makes sense to me to allow this...

This is only a sliver of where I and others (@darthscsi 👀 ) want to take parameters. However, this is the bare minimum cleanup that fixes a lot of weirdness...

> It seems like we need to support / demonstrate parameters in UInt widths at least to make this change? Yes. I totally missed this. Currently you _can_ do this...

I updated this with a couple of changes: 1. Parameters are now boxed with a `Param` indicator. This is done to sequester parameters into their own area. 2. To solve...

#147 improves how block quotations are rendered to make them look like RISC-V Specification commentary blocks (an italicized region with increased left and right indentation and a rule at the...

Thanks for the detailed post. The issue you bring up is slightly different from the issue I was worried about here. I'll comment on the issue I was worried about...

> I'll ask them why it hasn't been updated on the Anaconda repo. 👍 Sounds good. We aren't coordinating any releases through Anaconda (and I wasn't even aware that CIRCT...