There is some similar stuff in GHC already, to do with !. It is both an
infix operator and (in some contexts) a unary prefix to a function argument
f !x y = ...rhs...
See RdrHsSyn.splitBang.
Just possibly the same kind of stuff will help with ~?
S
| -Original Message-
|
| Now that I have a working GHC development environment (which was easier
| than thought thanks to the good documentation on the wiki), I am looking
| forward to work on ticket #7081 during the summer. When is the
| (approximate) deadline for feature patches for GHC 7.12?
Great! We don't have a
Austin Seipp wrote:
- If your bug is critical, please explain why! We really want to
kill showstoppers ASAP, because bugs are much cheaper to fix early. If
that's the case we can bump the priority if it's necessary to make
things clear.
I know Arm is not a tier 1 platform, but I think
- If your bug is critical, please explain why! We really want to
kill showstoppers ASAP, because bugs are much cheaper to fix early. If
that's the case we can bump the priority if it's necessary to make
things clear.
#10443 is critical to me, it prevents the installation of ghc-mod, which
Am Freitag, den 05.06.2015, 10:44 + schrieb Simon Peyton Jones:
Now that I have a working GHC development environment (which was easier
than thought thanks to the good documentation on the wiki), I am looking
forward to work on ticket #7081 during the summer. When is the
(approximate)
But if multiple versions of the same library can be linked into one
binary, then the binary sizes will increase and therefore the memory
usage might increase and even performance might decrease a bit if
the number of cache misses increase.
This is not in the current proposal. GHC knows how
I have written a new wiki page which tries to explicate these concepts:
https://ghc.haskell.org/trac/ghc/wiki/Commentary/Packages/Concepts
I haven't finished writing my proposal but one thing that I am going
to argue is that we are going to need *MORE* package identification
concepts (sorry
