So in practice using a parameter could be surprisingly very expensive? Are you supposed to thunk all your parameters before grabbing a resource? It seems like

So in practice using a parameter could be surprisingly very expensive? Are you supposed to thunk all your parameters before grabbing a resource? It seems like it would end up quite cumbersome. C# has object properties that can be values or functions. Etiquette dictates you don't query a database in an object property but I've seen it happen. I'm not even sure what the etiquette here would be. The entire point is to lazily evaluate slow things, right? But I guess its all just for IRs and the idea is a compiler is handling it all anyway?