You know these bugs, that disappear when you add logging?

Heisenbugs?

Race conditions? Cuz logging is so slow it makes order consistent.

@Lensflare Shrodingbugs?

@atheist or lazy evaluation

bites harder than concurrency or parallelism

or objects mutating state on fetch. Burns more than when you pee

Or the fact you call the function/serialising in the logging causing it to evaluate correctly

@netikras object doing WHAT????

https://youtube.com/watch/...

Maybe you should listen to the logging song

@netikras

> or objects mutating state on fetch.

This is so evil (or retarded, if not intentional)

@Lensflare yeah, but it's also normal in some cases. E.g. consuming an input stream (java, javascript) of an incoming request (as the request could be gigabytes in size, it might be impossible to store it in memory)

@netikras true. As long as it‘s explicitly specified and part of the design, I guess it’s ok.

Though we could argue if consuming a stream can be called "fetching" or if we should use a different term for that.

Fetching implies no mutation, imo.

@Lensflare well, the method says read(), not consume() 😁