Here is a nice discussion about fexprs:
http://lambda-the-ultimate.org/node/3640
On Tuesday, 26 April 2016 23:04:09 UTC+2, tbc++ wrote:
>
> Congradulations! You've discovered Fexprs! An ancient technology from a
> by-gone age: https://en.wikipedia.org/wiki/Fexpr
>
> On Tue, Apr 26, 2016 at 2:2
Wow ;-) now I know that I'm talking about fexprs ;-) So my propose is to
back them alive again. Let the new community consume them in new manner and
judge theirs usefulness.
On Tuesday, 26 April 2016 23:04:09 UTC+2, tbc++ wrote:
>
> Congradulations! You've discovered Fexprs! An ancient technolo
Congradulations! You've discovered Fexprs! An ancient technology from a
by-gone age: https://en.wikipedia.org/wiki/Fexpr
On Tue, Apr 26, 2016 at 2:23 PM, Olek wrote:
> Yes, the delay and force does the job. Now it would be nice to hide delay
> declaration in arguments destruction as already prop
Yes, the delay and force does the job. Now it would be nice to hide delay
declaration in arguments destruction as already proposed:
(den mycrazyif [ statement ~onsuccess ~onfailure ] ; nonsuccess and on
failure becomes delay objects
(if statement ; just evalutated with mycrazyif call
I'm not sure I fully understand your proposal, but when I really need lazy
evaluation (which is pretty rare) I reach for `delay` and `force`.
On Tuesday, 26 April 2016 16:41:08 UTC+1, Olek wrote:
>
> Hi!
>
> In short:
>
> I have noticed that in most cases I use macros only for lazy arguments
> e
Hi!
In short:
I have noticed that in most cases I use macros only for lazy arguments
evaluation. Why not to make something to use only this feature? It would be
light version of macro for clojurescript/clojure and easy to grasp for
newcomers and still powerful in programming (with that you cou
