Re: [Chicken-hackers] [PATCH 0/5][5] Generalize port directionality and add basic refinement types

* John Cowan [160709 19:03]: > > For situations when it's desirable to expose only one end of a > > pair, we could create a procedure like "extract-input-port" and > > "extract-output-port" from a bidirectional port. I'm not sure what > > good names would be for these. >

Re: [Chicken-hackers] [PATCH 0/5][5] Generalize port directionality and add basic refinement types

Peter Bex scripsit: > Regarding our earlier discussion, I think it's a good idea to now > change all procedures which return both an input and an output port to > return a bidirectional port instead. This makes it less of a hassle > to get these values; you wouldn't need receive,

[Chicken-hackers] [PATCH 0/5][5] Generalize port directionality and add basic refinement types

Hi hackers, Here is a quite large patchset that, at its heart, adds support for multidirectional ports by converting the simple boolean flag indicating whether a port is for input or output to a bitmap. It also adds `input-port-open?` and `output-port-open?` procedures for testing whether a port