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

discrepancy in description for Foldw/MatchW for Either vs TaskEither #1955

Open
FilipLaz opened this issue Nov 7, 2024 · 0 comments
Open

Comments

@FilipLaz
Copy link

FilipLaz commented Nov 7, 2024

📖 Documentation

Looking at the documentation I am confused in method signature for Foldw/MatchW between Either and TaskEither

Either

foldW and matchW have exact same signature

foldW

export declare const foldW: <E, B, A, C>(onLeft: (e: E) => B, onRight: (a: A) => C) => (ma: Either<E, A>) => B | C

matchW

export declare const matchW: <E, B, A, C>(onLeft: (e: E) => B, onRight: (a: A) => C) => (ma: Either<E, A>) => B | C

TaskEither

foldW and matchW are different

foldW

export declare const foldW: <E, B, A, C>(
    onLeft: (e: E) => T.Task<B>,
    onRight: (a: A) => T.Task<C>
) => (ma: TaskEither<E, A>) => T.Task<B | C>

matchW

export declare const matchW: <E, B, A, C>(
    onLeft: (e: E) => B,
    onRight: (a: A) => C
) => (ma: TaskEither<E, A>) => T.Task<B | C>

What would be an adequate explanation for this?

@FilipLaz FilipLaz changed the title Discrepany in description for Foldw/MatchW for Either vs TaskEither discrepancy in description for Foldw/MatchW for Either vs TaskEither Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant