<whitequark[cis]>
please respond with your comments or disposition: merge or close
<zyp[m]>
unless anybody else has any discussion points, my disposition is still merge :)
<tpw_rules>
stupid qs without enough context, what happens to the non-used pieces? they are simply not hooked up and take the same init value as in RFC55? i guess normal mechanisms stop you from using the e.g. output half twice on the original port?
<zyp[m]>
this happens before the IO buffer construction
<Wanda[cis]>
... init value?
<tpw_rules>
zyp[m]: that answers it, thank you.
<Wanda[cis]>
I don't think I understand the question
<zyp[m]>
«what happens to the output signals when you make an IO port into an input?»
<zyp[m]>
and the answer is there is no output signals, because no IO buffer is constructed
<Wanda[cis]>
oh.
<Wanda[cis]>
yeah. the answer is that nothing at all happens until you actually construct a buffer using the port
<Wanda[cis]>
you can already construct an output-only io.Buffer on a bididrectional port; this RFC merely provides a wrapper that prevents you from creating any other kind of buffer than output-only
<Wanda[cis]>
and if you try to use both the original and the new port, the result is the same as if you used the original port twice (ie. a double-use error)
<tpw_rules>
sounds good, thank you
<Wanda[cis]>
we actually have a very similar mechanism to the proposed one (creating a modified port out of an existing port): inverting a port via ~port; the rules are pretty much the same
<whitequark[cis]>
all right, disposition on RFC 79: merge
<whitequark[cis]>
thank you everyone, that is all for today
d_olex has quit [Remote host closed the connection]