Quick poll. Do you depend on the laziness of `memo...

# spek

[raniejade]

Quick poll. Do you depend on the laziness of memoized on your tests? https://github.com/spekframework/spek/pull/660 came up to eagerly evaluate memoized during the execution phase instead of evaluating on access. Options: 👌, 🚫 and 🙃 if you didn’t know that memoized is lazy.

[gildor]

I think that memoized should be lazy by default, argument to disable lazyness may be useful but not sure about this

[Nikky]

i declare them in order anyways.. so as long as they get executed in order of declaration i should be fine

[raniejade]

@gildor what are the benefits though?

[raniejade]

@Nikky yes, that’s roughly the plan.

This:

val foo by memoized { Foo() }
val bar by memoized { Bar() }

it("do something") { 
  assertEquals(foo.something(), bar.something())
}

is equivalent to (in terms of execution):

val foo = Foo()
val bar = Bar()
assertEquals(foo.something(), bar.something())