Lazy Eval in WolframLang

By Xah Lee. Date: .
Research Working Session: Tuesday, September 13, 2022 [Multicomputation]

am no expert, but i vote agaist lazy stuff.

Lazy eval is wholly against the nature of WolframLang. In WL, every thing is concrete, visible. Only few necessary exceptions such as sparse array, associations (which i think are mistakes). There is no programing language engineering byproducts such as references, float, linked list vs array, etc, which came out due to implementation efficiency issues.

The lazy eval is a byproduct of implementation efficiency. From this session, seeing all the lazy functions, it might be all consming into WL. I feel it's not possible to integrate lazy stuff that well into the whole WL.

Highly against the lazy stuff. If adding that, might as well as add other engineering byproducts such as references as value of list, and OOP, objects methods etc. These completely thwart the philosophy of WolframLang.

are there actually significant percentage of WolframLang users who want lazy eval?

WolframLang lazy eval 2022-09-13 9vqYj
WolframLang lazy eval 2022-09-13 9vqYj
WolframLang lazy eval 2022-09-13 J3K2M
WolframLang lazy eval 2022-09-13 J3K2M
WolframLang lazy eval 2022-09-13 T6svC
WolframLang lazy eval 2022-09-13 T6svC
WolframLang lazy eval 2022-09-13 QkCSg
WolframLang lazy eval 2022-09-13 QkCSg