abstract class Visitor[F[_], A, R] extends (Iterant[F, A]) => R
Implements the
Visitor Pattern
for interpreting the Iterant data structure.
This can be used as an alternative to pattern matching and is
used in the implementation of Iterant for performance reasons.
WARN: this being a class instead of a recursive function, it means that it often has to keep "shared state". Keeping shared state is great for performance, but breaks referential transparency, so use with care.
- Source
- Iterant.scala
Linear Supertypes
Ordering
- Alphabetic
- By Inheritance
Inherited
- Visitor
- Function1
- AnyRef
- Any
- Hide All
- Show All
Visibility
- Public
- Protected
Instance Constructors
- new Visitor()
Abstract Value Members
- abstract def fail(e: Throwable): R
Processes unhandled errors.
- abstract def visit(ref: Halt[F, A]): R
Processes Iterant.Halt.
- abstract def visit(ref: Last[F, A]): R
Processes Iterant.Last.
- abstract def visit[S](ref: Scope[F, S, A]): R
Processes Iterant.Scope.
- abstract def visit(ref: Concat[F, A]): R
Processes Iterant.Concat.
- abstract def visit(ref: Suspend[F, A]): R
Processes Iterant.Suspend.
- abstract def visit(ref: NextCursor[F, A]): R
Processes Iterant.NextCursor.
- abstract def visit(ref: NextBatch[F, A]): R
Processes Iterant.NextBatch.
- abstract def visit(ref: Next[F, A]): R
Processes Iterant.Next.
Concrete Value Members
- def andThen[A](g: (R) => A): (Iterant[F, A]) => A
- Definition Classes
- Function1
- Annotations
- @unspecialized()
- def apply(fa: Iterant[F, A]): R
- Definition Classes
- Visitor → Function1
- def compose[A](g: (A) => Iterant[F, A]): (A) => R
- Definition Classes
- Function1
- Annotations
- @unspecialized()
- def toString(): String
- Definition Classes
- Function1 → AnyRef → Any
This is the API documentation for the Monix library.
Package Overview
monix.execution exposes lower level primitives for dealing with asynchronous execution:
Atomictypes, as alternative tojava.util.concurrent.atomicmonix.catnap exposes pure abstractions built on top of the Cats-Effect type classes:
monix.eval is for dealing with evaluation of results, thus exposing Task and Coeval.
monix.reactive exposes the
Observablepattern:Observableimplementationsmonix.tail exposes Iterant for purely functional pull based streaming:
BatchandBatchCursor, the alternatives to Scala'sIterableandIteratorrespectively that we are using within Iterant's encodingYou can control evaluation with type you choose - be it Task, Coeval, cats.effect.IO or your own as long as you provide correct cats-effect or cats typeclass instance.