Jiuyang Liu

Yes, I'm also working on chipsalliance/chisel#3999 to provide a clear hardware interface among different projects recently. it won't be too long to finish. After finishing it, I think we can...

You can split it into a new `build.sc` build target for now, and I'll take a look at them one by one to propose a concrete plan for deprecating or...

Yes. Layer is doing good in firrtl spec. But at chisel level, I’m thinking is there some design pattern for it? e.g. aop for a same IO, and corresponding aspect...

This is tricky: seems Class/Object and Path API is happier with D/I API. Think about for each OM Class we instantiate under a Module, we cannot use `Path` API to...

Not actually, the problem is: > The rule is the paths in the OM dialect need to be hierarchically underneath the same "owning module" as the entities they target. https://github.com/llvm/circt/blob/6914bc6e0d11468c3fb11dfda74091f6e2e0306d/include/circt/Dialect/FIRRTL/OwningModuleCache.h#L18-L22....

> With the current SBT flow, every push to main publishes a SNAPSHOT based on the current commit. That wouldn't work with a version file. Similarly, the current flow for...

For those issue you described, I think maybe it’s a right time for chisel to deprecate native Windows support ;p

I do like this idea, and my suggestion is you can sending small APIs and PR to this [folder](https://github.com/chipsalliance/chisel/tree/main/stdlib/src/main/scala/chisel3/std), this is not released by we can release it in the...

> We don't know how to fix the issue better. cc @sequencer Please use D/I... I'm prototyping the new diplomacy framework, but that needs a large refactor...

From my mind: - All `LazyModule` should only be a `SerializableModule` that only depends on a `SerializableModuleParameter`. In this case, all `SerializableModule` can be safely instantiated via D/I. and is...