having a large number of versions of GHC out there can make it difficult
for library authors, package curators, and large open source projects, due
to variety of what people are using.
For point releases, if we do it right, this *should* not happen, since the
changes *should* be
RebindableSyntax
I thought this would work, but people seemed pretty sure we would need to do
more work than RebindableSyntax to get everything in place.
--
Stephen Paul Weber, @singpolyma
See http://singpolyma.net for how I prefer to be contacted
edition right joseph
signature.asc
of the project) is not an
unreasonable thing to do.
--
Stephen Paul Weber, @singpolyma
See http://singpolyma.net for how I prefer to be contacted
edition right joseph
signature.asc
Description: Digital signature
___
ghc-devs mailing list
ghc-devs
off that I can put in all of my builds.
--
Stephen Paul Weber, @singpolyma
See http://singpolyma.net for how I prefer to be contacted
edition right joseph
signature.asc
Description: Digital signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http
- --
Stephen Paul Weber, @singpolyma
See http://singpolyma.net for how I prefer to be contacted
edition right joseph
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBCAAGBQJULBgbAAoJENEcKRHOUZzeikQP/ir+JdnO5Hdfe2j13Ut4Plkx
cRBK9mbn5bXgojGS/0WZuDLl8A6wn4QlzgeG
' to create
the database with the correct format.
So, do I need an even newer version of cabal-install (HEAD maybe?)? Or does
cabal-install just not support GHC HEAD yet at all yet?
- --
Stephen Paul Weber, @singpolyma
See http://singpolyma.net for how I prefer to be contacted
edition right joseph
if that library should be required, but it does fix the problem.
So now I'm wondering if there's a way to tell my GHC build that when it is
built for this platform it should just always link against libcaps as well
as whatever else?
- --
Stephen Paul Weber, @singpolyma
See http://singpolyma.net for how I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I suppose that -XOverlappingInstances could mean silently honour
OVERLAPPABLE/OVERLAPPING pragmas, while lacking it would mean honour
OVERLAPPABLE/OVERLAPPING pragmas, but emit noisy warnings or even don't
honour them and warn.
But that is
and then eventually
(likely) be rejected by newer GHCs, thus requiring a prepropcessor in either
case.
--
Stephen Paul Weber, @singpolyma
See http://singpolyma.net for how I prefer to be contacted
edition right joseph
___
ghc-devs mailing list
ghc-devs
Somebody claiming to be Herbert Valerio Riedel wrote:
Does anyone actually still use/test those packages in HUGS?
I know lots of people still using HUGS.
(When) can that code be removed?
When enough features become standard that it becomes unnecessary ;)
--
Stephen Paul Weber, @singpolyma
anyway and the switch was not
difficult.
Did you have to seperately cross-compile libgmp first, or does android have
it by default?
--
Stephen Paul Weber, @singpolyma
See http://singpolyma.net for how I prefer to be contacted
edition right joseph
to build a cross-compiler for arm-linux just now and it complained that I
don't have curses for terminfo :P
If anyone with an Android or other cross-compiler could test it out, that
would be awesome too, but I will keep poking.
--
Stephen Paul Weber, @singpolyma
See http://singpolyma.net for how I
GHC.
Can one of the people working on Android and/or Raspberry Pi ports try this
code out and let me know if it works for you? I'll try to do a native
(non-cross-compile) build of GHC with integer-simple as well, to test this
on.
--
Stephen Paul Weber, @singpolyma
See http://singpolyma.net
}
This is because the source uses a feature that cannot be supported in
cross-compilation. The problematic line, however, can easily be removed.
It would be very useful to have a CPP macro defined by GHC that can be used
to enable/disable these sorts of features.
--
Stephen Paul Weber, @singpolyma
See
-base.
It would be great to have a portable base, without any GHC-specific
stuff in it. After all, modules like Control.Monad or Data.Foldable are
pure Haskell2010.
+1
--
Stephen Paul Weber, @singpolyma
See http://singpolyma.net for how I prefer to be contacted
edition right joseph
a standalone 'deriving instance' declaration,
so you can specify the instance context yourself
When deriving the instance for (Fractional CFloat)
Has anybody seen this with HEAD?
This may be a side effect of the fix for
http://hackage.haskell.org/trac/ghc/ticket/7569
--
Stephen Paul
/7519
This affects more than just Solaris.
--
Stephen Paul Weber, @singpolyma
See http://singpolyma.net for how I prefer to be contacted
edition right joseph
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
17 matches
Mail list logo