Timeline for Would using coroutines improve my code?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 18, 2019 at 5:10 | answer | added | Martin Maat | timeline score: 1 | |
| May 18, 2019 at 2:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 18, 2019 at 1:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 19, 2018 at 0:15 | answer | added | user321630 | timeline score: 1 | |
| Aug 24, 2016 at 10:52 | comment | added | user6245072 | That's a thing I didn't think of. Fair enough. Previously, the way the REPL for my language worked was: Try parsing this first line; if an "unfinished X" error occours, concatenate to another line and retry parsing; Repeat until no "unfinished X" error occours, then parse the whole text and interpret the generated structure. But this opens the way to far nicer solutions on that side. Thanks for pointing it out! | |
| Aug 24, 2016 at 10:42 | comment | added | CodesInChaos | Using co-routines you can suspend parsing in the middle of a message. That could be helpful when you parse large data that slowly arrives over time. (Though I'd consider redesigning the protocol in that case) | |
| Aug 24, 2016 at 10:01 | history | asked | user6245072 | CC BY-SA 3.0 |