Carter Schonwald <carter.schonw...@gmail.com> writes: > solution: lets call these registers what they are, instead of pretending > they're portable. we are not going to find the right abstraction in the > first go. lets not do that. first get it working sanely, then figure out > proper abstractions > I'm not sure I understand what you are suggesting here. Are you suggesting we rename the types and primops in the Haskell interface? Some deeper change in semantics? Their treatment in the compiler backend? Something else entirely?
I'm lost. Cheers, - Ben
signature.asc
Description: PGP signature
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs