| Turns out that I need a larger example to trigger the bug. I can
| reliable trigger it using the unordered-containers library. I won't bore
| you with the details. The workaround I need is this:
|
| forall x. integerToWord (smallInteger x) = int2Word# x
So why not just add that rule
It turns out that running 'perl boot' in symlinked directory (ghc-build) is not
enough. I had to
run 'perl boot' in the original ghc-working dir and now configure succeedes in
ghc-build.
Janek
___
Glasgow-haskell-users mailing list
Hi,
I find our tests to be quite hard to navigate, as the majority have
names like tc12345.hs or some such. I suggest we instead use
descriptive names like GADT.hs or PrimOps.hs instead. What do people
think?
-- Johan
___
Glasgow-haskell-users mailing
(This belongs on cvs-ghc, or the upcoming ghc-devs.)
| I find our tests to be quite hard to navigate, as the majority have
| names like tc12345.hs or some such. I suggest we instead use descriptive
| names like GADT.hs or PrimOps.hs instead. What do people think?
We've really moved to a naming
* Simon Peyton-Jones simo...@microsoft.com [2012-12-18 10:32:39+]
(This belongs on cvs-ghc, or the upcoming ghc-devs.)
| I find our tests to be quite hard to navigate, as the majority have
| names like tc12345.hs or some such. I suggest we instead use descriptive
| names like GADT.hs or
On 2012-12-18 13:33, Roman Cheplyaka wrote:
But I wonder what if one wants to create a test preventively (say,
for a
new feature), and there isn't actually any bug to create a ticket
for?
Roman
In that case, I would open a ticket with the type 'feature request' to
get the right ticket
On 15/12/12 14:46, Jan Stolarek wrote:
OK, so how can we improve it?
First of all I think that materials in the wiki are well organized for people
who already have
some knowledge and only need to learn about particular things they don't yet
know. In this case I
think it is fine to have wiki
On 18/12/12 10:09, Jan Stolarek wrote:
It turns out that running 'perl boot' in symlinked directory (ghc-build) is not
enough. I had to
run 'perl boot' in the original ghc-working dir and now configure succeedes in
ghc-build.
You shouldn't do that, because now you have build files in your
On 18/12/12 12:33, Roman Cheplyaka wrote:
* Simon Peyton-Jones simo...@microsoft.com [2012-12-18 10:32:39+]
(This belongs on cvs-ghc, or the upcoming ghc-devs.)
| I find our tests to be quite hard to navigate, as the majority have
| names like tc12345.hs or some such. I suggest we instead
| It seems that many informations in the wiki are duplicated. There are
| two pages about
| repositories:
| http://hackage.haskell.org/trac/ghc/wiki/Repositories
| http://hackage.haskell.org/trac/ghc/wiki/WorkingConventions/Repositori
| es (after reading the first one source tree started to
The 2 approaches are not mutually exclusive.
ticket#_description.hs
tc12345_GADT.hs
On Tue, Dec 18, 2012 at 6:22 AM, Simon Marlow marlo...@gmail.com wrote:
On 18/12/12 12:33, Roman Cheplyaka wrote:
* Simon Peyton-Jones simo...@microsoft.com [2012-12-18 10:32:39+]
(This belongs on
On 18/12/12 15:51, Simon Peyton-Jones wrote:
| It seems that many informations in the wiki are duplicated. There are
| two pages about
| repositories:
| http://hackage.haskell.org/trac/ghc/wiki/Repositories
| http://hackage.haskell.org/trac/ghc/wiki/WorkingConventions/Repositori
| es
Dnia wtorek, 18 grudnia 2012, Simon Marlow napisał:
On 18/12/12 10:09, Jan Stolarek wrote:
It turns out that running 'perl boot' in symlinked directory (ghc-build)
is not enough. I had to run 'perl boot' in the original ghc-working dir
and now configure succeedes in ghc-build.
You
So the first page here tells you how to get a single source tree so that
you can build it. The second page tells you how to create a 2-tree
setup for use with GHC's validate; the latter is aimed at people doing
lots of GHC development (which is why it's under WorkingConventions).
I think that
14 matches
Mail list logo
