tpb has quit [Remote host closed the connection]
tpb has joined #symbiflow
az0re has joined #symbiflow
citypw has joined #symbiflow
az0re has quit [Quit: Leaving]
Degi has quit [Ping timeout: 272 seconds]
Degi has joined #symbiflow
alexhw has quit [Remote host closed the connection]
citypw has quit [Ping timeout: 240 seconds]
OmniMancer has joined #symbiflow
phire has quit [Read error: Connection reset by peer]
phiren has joined #symbiflow
promach3 has quit [Quit: killed]
unrznbl[m] has quit [Quit: killed]
xobs has quit [Quit: killed]
bluecmd[m] has quit [Quit: killed]
synaption[m] has quit [Quit: killed]
xobs has joined #symbiflow
synaption[m] has joined #symbiflow
promach3 has joined #symbiflow
unrznbl[m] has joined #symbiflow
bluecmd[m] has joined #symbiflow
alexhw has joined #symbiflow
alexhw has quit [Client Quit]
alexhw has joined #symbiflow
OmniMancer has quit [Quit: Leaving.]
epony has quit [Quit: reconf]
epony has joined #symbiflow
epony has quit [Max SendQ exceeded]
epony has joined #symbiflow
epony has quit [Quit: QUIT]
krogozinski_ has quit [Ping timeout: 265 seconds]
krogozinski has joined #symbiflow
epony has joined #symbiflow
<mithro> OpenRAM on SKY130 talk from Matt as part of FOSSi Foundation DialUp talk series is starting in 10 minutes -- https://youtu.be/9Lw83kFtnc4
<mithro> mkurc: Did my comment on https://github.com/SymbiFlow/python-symbiflow-v2x/issues/85 make sense?
<sf-slack> <mkurc> @mithro Yes it does. I just wasn't aware of the (* carry *) attribute.
<sf-slack> <kgugala> actually it is listed in the comment in top of the V2X file
<sf-slack> <kgugala> TBH i'd be good to extract those comments and create proper documentation
<sf-slack> <kgugala> @mkurc can you log an issue about it?
<mithro> I thought I had test cases with documentation
<mithro> But maybe that never got merged...
<mithro> mkurc: Is everything in #85 answered then?
<sf-slack> <mkurc> Most of them are documented through examples
<sf-slack> <mkurc> I think that what Karol has in mind is list of all of them in the documentation just like the one on the top of the code.
<sf-slack> <kgugala> yep
<sf-slack> <kgugala> I think we can create automatic rst documentation from examples
<sf-slack> <kgugala> and publish it on RTD
<sf-slack> <mkurc> @mithro Yep
<mithro> The useful thing about `(* carry *)` attribute is that when drawing diagrams we can use it as a hint that the pins should be running top<-to->bottom rather than left<-to->right
<mithro> kgugala: Yeah the docstrings should also be published to rst
<sf-slack> <mkurc> Ok. I'll file an issue about the docstring documentation
<sf-slack> <kgugala> @mkurc thanks
<_whitenotifier-f> [python-symbiflow-v2x] mkurc-ant opened issue #86: Make V2X code docstrings apprear in the generated documentation - https://git.io/JT0L5
tcal has quit [Quit: Connection closed for inactivity]
az0re has joined #symbiflow
TMM has quit [Remote host closed the connection]
TMM has joined #symbiflow