[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-hackers] [PATCH] Nicer port direction error messages
From: |
Evan Hanson |
Subject: |
[Chicken-hackers] [PATCH] Nicer port direction error messages |
Date: |
Thu, 30 Jun 2016 23:33:56 +1200 |
As pointed out by Peter on IRC, providing a hint about what kind of port
is expected when the wrong one is given is valuable from a
user-friendliness point of view, so this restores the error messages for
the typical input- and output-only cases, and uses the more general
wording only when the required direction isn't one of those.
Cheers,
Evan
- [Chicken-hackers] [PATCH 0/5][5] Generalize port directionality and add basic refinement types, Evan Hanson, 2016/06/30
- [Chicken-hackers] [PATCH 2/5] Add input-port-open? and output-port-open? procedures, Evan Hanson, 2016/06/30
- [Chicken-hackers] [PATCH 5/5] Add new `make-bidirectional-port` procedure to ports unit, Evan Hanson, 2016/06/30
- [Chicken-hackers] [PATCH 3/5] Add basic refinement types, Evan Hanson, 2016/06/30
- [Chicken-hackers] [PATCH 1/5] Generalize port directionality, Evan Hanson, 2016/06/30
- [Chicken-hackers] [PATCH 4/5] Add scrutinizer test suite, Evan Hanson, 2016/06/30
- Re: [Chicken-hackers] [PATCH 4/5] Add scrutinizer test suite, felix . winkelmann, 2016/06/30
- [Chicken-hackers] [PATCH] Nicer port direction error messages,
Evan Hanson <=