On Mon, Nov 5, 2012 at 5:52 PM, Johan Tibell johan.tib...@gmail.com wrote:
The tricky part is to define the semantics of this pragma in terms of
Haskell, instead of in terms of Core. While we also need the latter, we
cannot describe the feature to users in terms of Core. The hard part is to
What if the strict code were to assume nothing is ever _|_, and result in
undefined behavior if it is? Kind of like a NULL pointer in C.
On Tue, Nov 6, 2012 at 8:36 AM, Jan-Willem Maessen jmaes...@alum.mit.eduwrote:
On Mon, Nov 5, 2012 at 5:52 PM, Johan Tibell johan.tib...@gmail.comwrote:
On Mon, Nov 05, 2012 at 02:52:56PM -0800, Johan Tibell wrote:
Hi all,
I would like to experiment with writing some modules (e.g. low-level
modules that do a lot of bit twiddling) in a strict subset of Haskell. The
idea is to remove boilerplate bangs (!) and instead declare the whole
module
On Mon, Nov 5, 2012 at 3:28 PM, Iustin Pop iu...@k1024.org wrote:
Did you mean here it's still possible to define _lazy_ arguments? The
duality of !/~ makes sense, indeed.
Yes, it would be nice to still make arguments explicitly lazy, using ~.
___
