Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schedule forked types were not flipped in 2.3 #2146

Closed
riordanpawley opened this issue Feb 14, 2024 · 1 comment
Closed

Schedule forked types were not flipped in 2.3 #2146

riordanpawley opened this issue Feb 14, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@riordanpawley
Copy link
Contributor

What version of Effect is running?

2.3.5

What steps can reproduce the bug?

Use scheduleForked

What is the expected behavior?

No response

What do you see instead?

/**
 * Runs this effect according to the specified schedule in a new fiber
 * attached to the current scope.
 *
 * @since 2.0.0
 * @category repetition / recursion
 */
export const scheduleForked: {
  <R2, Out>(
    schedule: Schedule.Schedule<R2, unknown, Out>
  ): <A, E, R>(self: Effect<A, E, R>) => Effect<Scope.Scope | R2 | R, never, Fiber.RuntimeFiber<Out, E>>
  <R, E, A, R2, Out>(
    self: Effect<A, E, R>,
    schedule: Schedule.Schedule<R2, unknown, Out>
  ): Effect<Scope.Scope | R | R2, never, Fiber.RuntimeFiber<Out, E>>
} = circular.scheduleForked

Additional information

No response

@riordanpawley riordanpawley added the bug Something isn't working label Feb 14, 2024
@riordanpawley
Copy link
Contributor Author

#2148

@gcanti gcanti closed this as completed Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants