00:02 <_whitenotifier-e> [amaranth] whitequark closed pull request #1318: CI: fix coverage submission - https://github.com/amaranth-lang/amaranth/pull/1318

01:47 <eigenform> i think i'm a little confused about why Flow.In() should flip inner signature members https://gist.github.com/eigenform/1c992270d1d5598566a89aabd45c0d3d

01:49 <eigenform> this seems intelligible to me, but it tells me there are multiple drivers on req.ready (presumably because it's actually flipped to an input?)

01:50 <eigenform> (or maybe I'm just misusing Signature here?)

09:23 <zyp[m]> <eigenform> "(or maybe I'm just misusing..." <- yes, the idea of a signature is that it's always seen from the perspective of an initiator/producer

09:25 <zyp[m]> in other words, Out in a signature indicates data flow from initiator to responder or producer to consumer and an Out member with that signature in a component would indicate it is an initiator/producer for that interface, while a component with an In member of the same component would be a responder/consumer

09:27 <zyp[m]> so for that reason you shouldn't have RequestConsumer and ResponseProducer signatures, just Request and Response, and your request handler module should have In(Request()) and Out(Response()) members

09:28 <zyp[m]> while a module issuing requests and awaiting responses would have Out(Request()) and In(Response())

09:29 <zyp[m]> and the data member in both of the two signatures should be Out

10:35 <eigenform> ah, perfect - thank you! .. i guess i should've read the docs harder, it *does* literally say that :|