Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
4.2k views
in Technique[技术] by (71.8m points)

ocaml - Infinite Lists / Streams in ReScript

I can't seem to find the correct typing for an infinite list in ReScript.

I first tried:

type rec stream<'a> = ('a, () => ('a, stream<'a>))

Which was incorrect because ReScript thought the type was cyclic. So instead I tried:

type rec stream<'a> = ('a, Lazy.t<() => ('a, stream<'a>)>)

Which still gave me a type error.

Ultimately I am trying to get this piece of code to work but it fails due to the type signature being infinite.

let rec from: (int, Lazy.t<() => (int, Lazy.t<...>) = (x: int) => {
    (x, () => Lazy.from_fun(from(x+1)))
}

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Reply

0 votes
by (71.8m points)

If your only objection to Sequence is the Nil case, you can define

type rec stream<'a> = { x:'a, next:() => stream<'a> }

The difference with your definition is that we are creating a new recursive type, rather than trying to define a recursive type expression.

EDIT:

The difference between using a tuple or a record is that tuples are structurally typed whereas records are nominally typed.

This changes everything in term of equality and identity.

In particular the original definition can be read as

type stream0<'a> = ('a, () => 'b ) as 'b

Then whenever one wants to compare a type stream0<'a> with a tuple type, it might be needed to expand this abbreviation an unbounded number of time.

For instance, this function is well-typed.

let f: stream0<int> => (int, ()=>(int,() => _)) = (x) => x

or this one:

let app_once = ((x,next)) => next ()

One important consequence here is that it is possible to use a stream0<'a> in a context where a finite stream was expected. In other words, there are many have many potential equality between a stream0<'a> and a finite version of stream0<'a>.

Contrarily, the record definition of stream<'a> create a new and distinct type constructor stream. Consequently, a stream<'a> can only ever be equal to stream<'a>. In other words, a function designed for a stream<'a>

let app_once  = {x;next} => next(())

cannot work with the type

type one_stream<'a> = { x:'a, next:() => ('a, ()) }

In practice, the recursive type of stream0<'a> and its many type equalities is more bothersome than useful, and such recursive types are disabled by default.


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
OGeek|极客中国-欢迎来到极客的世界,一个免费开放的程序员编程交流平台!开放,进步,分享!让技术改变生活,让极客改变未来! Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

1.4m articles

1.4m replys

5 comments

57.0k users

...