4 ms·
Note: I wrote this yesterday after I wrapped my hands around coroutines. This is a work in progress (even if it's already fully working) I'll take any remarks h
by matt42 9y ago
Note: I wrote this yesterday after I wrapped my hands around coroutines. This is a work in progress (even if it's already fully working) I'll take any remarks here.
- notfed 9y agoSince you asked, I suggest running your readme through a spell checker. I didn't bother looking further than that.
- bjoli 9y agoNot everyone has English as a first or even second language. No bothering because of spelling seems like a good way to filter out some cool pieces of code.
- krotton 9y agoWith some potentially unreadable documentation. Spoken language is not less important than programming languages (and interestingly, from my experience, there seems to be at least some correlation between caring about either).
- matt42 9y agoI did not spend too much time writing the documentation because of the simplicity of the library. I thought that the tcp echo example would be enough. But I'll spend more time in the Readme, at least fixing the language issues :)
- nitely 9y agoSounds like a good way to filter out a certain kind of users.