Scala Maybe

I wrote a Maybe (a lazy Option[T]) that I can use in Scala. Scala Maybe … because I wanted a lazy variant of Option[+T]. I had a use case in mind at the time, but, since then; I’ve taken another approach. Since writing this,I’ve found an explanation of Monads that groks with me and multiple other places where “lazy is better” and I preffer (my) Maybe[T] over Option[T]. package peterlavalle /** * like Option[+A] but lazy */ trait Maybe[+T] { /** * however we're implemented; ensure that any operations leading up to now are only called "once" */ def cache: Maybe[T] /** * Apply some operation to the value, and, return a new monad.

Scala Extractors

Scala’s extractors and unapply() represent a concept that I haven’t grok’ed until now. Most demonstrations seem to be too long or use the same types everywhere. Here are my thoughts on the concept; val a: C = ??? val i: I = ??? i match { case a(f: O) => ??? } This will try to call the below method class C { def unapply(i: I): Option[O] = ??? } There’s some more flexibility;

(Scala) Delay Run

I wrote a threading primitive and I’m very pleased with it. I plan to wrap all of my “save file” things in this, from now on. Delay Run This class acts as a sort of “once inactive for X do Y” pattern. In my design, I’m wrapping my save actions in it and triggering schedule() after practically every edit. The class is passed a delay: Long value to specify how long to actually wait - I’m using 1.