Re: new ForeignPtr without finalizers

Manuel M T Chakravarty wrote:
 > [ newForeignPtr / addForeignPtrFinalizer argument order ]
 > This is the last outstanding issue. Shall we swap? I am torn. The
 > swapped argument order seems more appropriate, but it will break
 > code. Shall we have one more breakage before it's all frozen?

I think that FFI API breakage is effectively a non-issue: Try some
non-trivial FFI code which is older than a few months and you'll
either abandon portability or use #ifdefs. :-[ So I vote for swapping,
too. (Note that GreenCard has to be changed, too, in case we agree on
this.)

Cheers,
    S.