Harry Garrood
Harry Garrood
There's also an FFI page under "language". I think we should try to put it all under the language one.
I think if we can have the compiler take the view that empty data declarations for types with opaque representations are fine, and if we can add better support for...
> Roles may not be defined on uninhabited types (you can't coerce them if they can't exist!) I’m not sure this works - consider: ```purescript data Void1 a coerce (Nothing...
I can’t think of a reason to give Void1 a role other than phantom off the top of my head, but I don’t find the argument that persuasive - maybe...
I like your proposal otherwise, although I'm a bit reticent to add syntax like `data Effect a = foreign` when you can already express that with what we have in...
I also don't feel strongly that one is preferable to the other; in this case I think I'm trying to take a more pragmatic approach of considering where the language...
Yep, I think the newtype runtime representation guarantee is already present across all backends, because features like `derive newtype` and `Coercible` already rely on it.
I’d prefer to leave `foreign` as-is but possibly move it to contrib. There’s a bunch of code which depends on it and I personally don’t consider these flaws serious enough...
I completely agree; please don’t read my previous comment as an intention to deprecate other backends. :)
There's already an issue for this, isn't there?