5 replies

Unexpected behavior with `Schema.Void` encoding non-`undefined` values

Hi here! Is it known that

Schema.Void

Schema.Void

can encode things that are not

undefined

undefined

in something that is not

undefined

undefined

Here's an example of such a thing (playground here):

import { Schema } from "effect"

const foo = (f: () => void) => Schema.encodeSync(Schema.Void)(f()) 

console.log(foo(() => 'bar'))
// => logs "bar"

import { Schema } from "effect"

const foo = (f: () => void) => Schema.encodeSync(Schema.Void)(f()) 

console.log(foo(() => 'bar'))
// => logs "bar"

I would have naively expected that

undefined

undefined

would be the encoded value in any case.
That's a bit tricky as in Typescript, a void in the return value of a function does not enforce that it will not return something.

Effect Community•4mo ago•

5 replies

Vincent François

Unexpected behavior with `Schema.Void` encoding non-`undefined` values

Hi here! Is it known that

Schema.Void

Schema.Void

can encode things that are not

undefined

undefined

in something that is not

undefined

undefined

Here's an example of such a thing (playground here):

import { Schema } from "effect"

const foo = (f: () => void) => Schema.encodeSync(Schema.Void)(f()) 

console.log(foo(() => 'bar'))
// => logs "bar"

import { Schema } from "effect"

const foo = (f: () => void) => Schema.encodeSync(Schema.Void)(f()) 

console.log(foo(() => 'bar'))
// => logs "bar"

I would have naively expected that

undefined

undefined

would be the encoded value in any case.
That's a bit tricky as in Typescript, a void in the return value of a function does not enforce that it will not return something.

Unexpected behavior with `Schema.Void` encoding non-`undefined` values

Similar Threads

Unexpected behavior with `Schema.Void` encoding non-`undefined` values

Similar Threads

Similar Threads

Similar Threads