what about this loittle patch?
diff --git a/rts/posix/OSMem.c b/rts/posix/OSMem.c
index 125ae10..edb240a 100644
--- a/rts/posix/OSMem.c
+++ b/rts/posix/OSMem.c
@@ -145,6 +145,7 @@ my_mmap (void *addr, W_ size, int operation)
kern_return_t err = 0;
ret = addr;
+(void)prot;
Would someone feel able to open a Trac ticket summarising this thread (as
well as pointing to it), and making a proposal?
Done: https://ghc.haskell.org/trac/ghc/ticket/10733
___
ghc-devs mailing list
ghc-devs@haskell.org
I'm sure that would work, but I'm worried this is a symptom of a deeper
problem. Does anyone know what's going on here? This is holding up two patches
of mine.
Thanks!
Richard
On Aug 3, 2015, at 10:28 AM, Gabor Greif ggr...@gmail.com wrote:
what about this loittle patch?
diff --git
Like this?
Either use a type annotation to specify what 't0' should be
based on these potential instance(s):
instance Foo Bar -- Defined in 'Foo.Bar'
... and possibly more from other modules that
the compiler has not yet encountered
or define the required
On 2015-08-02 at 23:17, Reid Barton rwbar...@gmail.com wrote:
It may be worth noting that the existing error message is actually
technically
correct, in the sense that what would be needed for the program to compile
is exactly an instance of the form instance Foldable t where Then the
Hello,
what Reid says is exactly right---the issue is not really about what
instances are present, the problem is that GHC can't determine how to
instantiate `t0`.
Perhaps a more direct way to describe this is as follows:
Failed to infer type `t0`
while solving constraint `Data.String.IsString
On Mon, Aug 3, 2015 at 12:43 AM, Phil Ruffwind r...@rufflewind.com wrote:
I think the error message could be made clearer simply by emphasizing the
fact
that type ambiguity over the lack of instances.
Ambiguous type variable 't0' arising from a use of
elem :: a - t0 a - Bool
On 2015-08-03 at 04:43, Phil Ruffwind r...@rufflewind.com wrote:
I think the error message could be made clearer simply by emphasizing the fact
that type ambiguity over the lack of instances.
Ambiguous type variable 't0' arising from a use of
elem :: a - t0 a - Bool
caused by
On Mon, Aug 3, 2015 at 12:45 PM, Daniel Bergey ber...@teallabs.org wrote:
I thought GHC would infer the type when only one instance is in scope,
at least in some cases, like IsString. But I could well be wrong about
that.
Typeclasses are open-world; this is not a safe assumption, since
Hi devs,
In a (almost) clean validate on my MacOS 10.8 machine, I see this:
{{{
rts/posix/OSMem.c: In function 'my_mmap':
rts/posix/OSMem.c:109:15: error:
error: variable 'flags' set but not used [-Werror=unused-but-set-variable]
int prot, flags;
^
Would someone feel able to open a Trac ticket summarising this thread (as well
as pointing to it), and making a proposal?
Thanks
Simon
| -Original Message-
| From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Daniel
| Bergey
| Sent: 03 August 2015 17:47
| To: Phil
11 matches
Mail list logo
