Dan Fritchman

Example: ```python @h.generator def Big(params: Params) -> h.Module: @h.module class Unit: # Unit cell, used a handful of times in `Big` below. # The important part: *also depends on `params`*...

In general, everything that might desirably be a parameter, has some desirability to be hashed. Things like `Include` and `Lib` currently can't, just because they have a mutable `name` attribute...

The problem: - A circuit is principally defined in Hdl21 - We then, somehow, get some other legacy-language representation of it (e.g. from a layout-extraction) - It'd be nice to...

We have a use case which: * Does not (we think) need any Hdl21 VLSIR conversions * Needs a different version of protobuf, which conflicts with VLSIR's The few options...

Hdl21 isn't especially "API heavy"; unlike, say, numpy, it doesn't have 5000 public functions with 15 arguments each. Accordingly we've never used automatic doc-generation. The docs instead have a more...

Example: ```python @h.module class M: i = h.Input() o = h.Output() s = h.Signal() ``` There is a similar-looking, but not-working, alternative one might write like so: ```python @h.module class...

https://github.com/dan-fritchman/Hdl21#spice-class-simulation Says: > Class-based Sim definitions retain all class members which are SimAttrs and drop all others. Non-SimAttr-valued fields can nonetheless be handy for defining intermediate values upon which the...

Example: ```python @h.module class M: n = 5 i = h.Input(width=n) M.n #

Re: ```python class Tb: # Seems to be a requirement of a 'Tb' to have a "single, scalar port". VSS = h.Port() ``` That fact, in contrast, looks like it...