3 ms·
Thanks. But I'm I wrong to assume that this could be worked around by two additional processes and channels?
by Rochus 3y ago
Thanks. But I'm I wrong to assume that this could be worked around by two additional processes and channels?
- 082349872349872 3y agoBy what means would the two additional processes share the variable state? (I come from the pure message passing tradition and don't know much about Go so this may be a moot objection) FWIW Hoare thinks it makes for a simpler system if it is always possible to rewrite any SEQ as a PAR and vice versa.
- Rochus 3y agoMeanwhile I got a sample to which there is no adequate solution with my current proposal as long as we should not close the channel: https://news.ycombinator.com/item?id=38768025 https://news.ycombinator.com/item?id=38768025. Here are two proposals for a SELECT procedure if you want to take a look at it: https://news.ycombinator.com/item?id=38767926 https://news.ycombinator.com/item?id=38767926