diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2016-03-19 15:57:10 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2016-03-19 15:57:10 -0700 |
| commit | 3ac523393d15d51b0fd1b042eab4f7cb539f68a9 (patch) | |
| tree | 4de3879dda5682a2509dea4af52ecabc1b6f14a1 /083scenario_screen_test.mu | |
| parent | 1f69d061c17d83b0a665c4fee2407fac1b714b68 (diff) | |
| download | mu-3ac523393d15d51b0fd1b042eab4f7cb539f68a9.tar.gz | |
2798 - experiment: split channels into two ends
This way when you pass one end to a function or routine, you can implicitly give it the right to either read or write the channel, but not both. The cost: code gets more convoluted, names get more convoluted. You can see this in particular in the test for buffer-lines. Let's see how it goes..
Diffstat (limited to '083scenario_screen_test.mu')
0 files changed, 0 insertions, 0 deletions