Skip to main content

Timeline for answer to What's the difference between a stream and a queue? by Heatwave

Current License: CC BY-SA 3.0

Post Revisions

11 events
when toggle format what by license comment
Dec 5, 2015 at 20:46 vote accept elliot42
Dec 5, 2015 at 20:46
Dec 1, 2015 at 15:33 comment added nanny @JBRWilkinson Sorry to poke you on this old question, somebody else answered it which bumped it to the top.
Dec 1, 2015 at 15:32 comment added nanny @JBRWilkinson That's not the case. In Scheme, (stream) returns an empty stream. Also, this answer is wrong, a stream is a data structure, streams may not have a source, and streams do not inherently contain any data, they may be nil or null or the empty list. See SRFI-41 for more info.
May 28, 2013 at 12:35 comment added Blrfl @JBRWilkinson: I suppose you could open a stream, send nothing through it and then close it.
May 25, 2013 at 14:21 comment added JBRWilkinson Yes, you're right - all data has to come from somewhere. Perhaps the actual point here is that a queue could be empty and a stream, by definition, is usually not?
May 24, 2013 at 11:16 comment added Blrfl @JBRWilkinson: Run without an argument, the data source for yes(1) is the embedded default string. Run with an argument, it's whatever provided the argument.
May 24, 2013 at 10:22 history edited Heatwave CC BY-SA 3.0
Typo
May 24, 2013 at 10:18 comment added JBRWilkinson The Unix 'yes' command looks like a stream but has no particular data source.
May 24, 2013 at 10:05 comment added Vatine There's actually a data structure called "stream", with (effectively) a list of data to consume, with a producer function at its tail, callable if you need more elements.
May 23, 2013 at 23:01 review First posts
May 24, 2013 at 0:59
May 23, 2013 at 22:45 history answered Heatwave CC BY-SA 3.0