It's likely I'm asking this question because I don't have a good understanding of how Operation Systems and I/O work!
A problem that occurs in Node is that printing large log statements will freeze the program. Can we make console printing async in deno?
mohsen1
All 5 comments
@mohsen1 I'd rather keep it synchronous for debugging now. In the future I would be open to changing that...
ry
on 31 Aug 2018
@ry @mohsen1 I think console should stay synchronous as it is elsewhere. I think we could have asynchronous console reading / writing through stdin and stdout streams with the Reader and Writer interfaces.
NewLunarFire
on 1 Sep 2018
as it is elsewhere
One thing to note here is that Chrome has async logging, at least for objects. They don't resolve until you expand them. But since you can't do that in the terminal, so that's there.
I think we could have asynchronous console reading / writing through stdin and stdout streams
I agree with this part.
MKRhere
on 7 Sep 2018
Now we have deno.stdout.write() and it's async.
kt3k
on 19 Jan 2019
I think we can close this @ry
bartlomieju
on 12 Feb 2019
Related issues
JosephAkayesi
路
3Comments
CruxCv
路
3Comments
zugende
路
3Comments
watilde
路
3Comments
kyeotic
路
3Comments
Most helpful comment
@ry @mohsen1 I think console should stay synchronous as it is elsewhere. I think we could have asynchronous console reading / writing through stdin and stdout streams with the Reader and Writer interfaces.