I was running into a problem with using streams in typed racket, where I was 
using the Sequenceof type to represent streams, and they got turned into 
non-stream sequences, which don’t work for stream-specific operations.

I think what's causing it is this:
#lang racket
(define/contract my-stream
  (sequence/c any/c)
  (stream 1 2 3))
(stream? my-stream)
This produces #f.

While I can sort of understand why it’s doing this, would it make sense to 
change this so that it keeps it a stream?

It seems like most of the other sequence operations specify that they preserve 
stream-ness, so is there any reason this doesn’t?


-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to