[GHC] #8281: The impossible happened: primRepToFFIType
GHC
ghc-devs at haskell.org
Tue May 23 02:59:20 UTC 2017
#8281: The impossible happened: primRepToFFIType
-------------------------------------+-------------------------------------
Reporter: tibbe | Owner: (none)
Type: bug | Status: new
Priority: high | Milestone: 8.4.1
Component: Compiler | Version: 7.6.2
Resolution: | Keywords:
Operating System: Unknown/Multiple | Architecture:
Type of failure: Compile-time | Unknown/Multiple
crash | Test Case:
Blocked By: | Blocking:
Related Tickets: | Differential Rev(s):
Wiki Page: |
-------------------------------------+-------------------------------------
Comment (by winter):
Replying to [comment:24 bgamari]:
> > what is stopping GHCi supporting unsafe FFI calls?
>
> If I understand Simon correctly, the answer is probably "nothing".
However, it's more a question of whether we want to change the semantics
of "unsafe" foreign calls (something which would require the involvement
of the Haskell Prime committee, if to be done properly). I can see the
argument for `unsafe` not placing any new obligations on the compiler and
think there's little reason to push for such a change.
>
> I do think, however, that it is important that we have a `unsafenogc`
call type for the reason you describe.
That's a reasonable solution. But as simon pointed out, we're too vague on
`unsafe` FFI calls before, it's not a big deal to give a more clear
semantics, is it? After all we have been relying that semantics for years,
it's more costly to add new FFI keyword and change all the libraries.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8281#comment:25>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list