What you probably want are type level integers (naturals)
Yury Sulsky used them in the message above - basically you can't use
literal numbers 1,2,3,... etc as they are values of type Int (or
Integer, etc...) instead you have to use type level numbers:
data One
data Two
Work is ongoing for type
Aleksandar Dimitrov wrote:
I've been kicking around the idea of re-implementing HList on the basis of the
new DataKinds [1] extension.
The current HList already uses DataKinds (and GADTs), to the extent
possible with GHC 7.4 (GHC 7.6 supports the kind polymorphism better, but
it had a critical
Dan Doel dan.doel at gmail.com writes:
However, another thing to consider is that getting rid of data type
contexts was accepted into the language standard.
... which means that implementers should be free to fix data type contexts
however they like, as they are now complier extensions which
On Sat, 27 Apr 2013 22:56:32 +0200, John MacFarlane j...@berkeley.edu
wrote:
Hello café:
I'd very much like to get text-icu working on Windows, as then I could
ship
pandoc binaries that do proper unicode collation in bibliographies. But
I'm
having a devil of a time. This may be due to
Aleksandar Dimitrov aleks.dimitrov at gmail.com writes:
Hi Aleksandar, I was hoping that Oleg himself would answer the second part
of your post, as he did the part re DataKinds:
Here's one thing I don't like about the current way HList-based
extensible record are represented (and used
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/04/13 00:08, Joe Nash wrote:
Managed not to send to all:
I think the reason markdown was the original suggestion was due to
the fact it is a very widespread and popular syntax, and as Johan
commented in the original thread, has to an
On 28 Apr 2013 11:33, Mateusz Kowalczyk fuuze...@fuuzetsu.co.uk wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/04/13 00:08, Joe Nash wrote:
Managed not to send to all:
I think the reason markdown was the original suggestion was due to
the fact it is a very widespread and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/04/13 11:57, Joe Nash wrote:
On 28 Apr 2013 11:33, Mateusz Kowalczyk fuuze...@fuuzetsu.co.uk
wrote:
If the flexibility of having it pandoc compatible is a desired
feature, can this not be achieved through implementing markdown
for
On 27/04/13 15:21, Christopher Howard wrote:
Hi. I've got this work situation where I've got to do all my work on
/ancient/ RHEL5 systems, with funky software configurations, and no root
privileges. I wanted to install GHC in my local account, but the gnu
libc version is so old (2.5!) that I
On Sun, Apr 28, 2013 at 3:59 AM, harry volderm...@hotmail.com wrote:
Dan Doel dan.doel at gmail.com writes:
However, another thing to consider is that getting rid of data type
contexts was accepted into the language standard.
... which means that implementers should be free to fix data
I think it's worth backing up here, and remembering the original point
of the proposal, by thinking about what is and isn't a goal. I think
I'd classify things like this:
Goals:
- Use a lightweight, common, and familiar core syntax for simple formatting.
- Still allow haddock-specific stuff like
Brandon Allbery allbery.b at gmail.com writes:
... which means that implementers should be free to fix data type contexts
however they like, as they are now complier extensions which won't conflict
with standard Haskell.
Except that people do build older programs with newer Haskell
On Sun, Apr 28, 2013 at 10:29 AM, gs volderm...@hotmail.com wrote:
Brandon Allbery allbery.b at gmail.com writes:
... which means that implementers should be free to fix data type
contexts
however they like, as they are now complier extensions which won't
conflict
with standard Haskell.
Greetings,
I am a Computer Science student from Argentina. I am interested in working
this summer in a project related to Haskell for the Google Summer of Code.
I have been discussing my idea with Michael Snoyman in order to have a
clearer idea. Now, I would like to know the community interest in
Thanks all for your solutions!
Here is a summary:
- floating a value to the top level; then with -Wall GHC will give the type
since we didn't give a value,
- adding :: () to the value to check, GHC will complain equally,
- using TemplateHaskell (hereunder),
- waiting for the release of the next
Alexander Solla alex.solla at gmail.com writes:
I do not support that criterion. We use theory to ENSURE that no
real-world code will break.
By theoretical example, I meant something which you would never expect to
find in use. Perhaps it was a poor choice of wording in an academically
On Sun, Apr 28, 2013 at 10:55 AM, gs volderm...@hotmail.com wrote:
Alexander Solla alex.solla at gmail.com writes:
I do not support that criterion. We use theory to ENSURE that no
real-world code will break.
By theoretical example, I meant something which you would never expect to
find
Hello all,
So I'm processing a large XML file which is a database of about 170k
entries, each of which is a reasonable enough size on its own, and I only
need streaming access to the database (basically printing out summary data
for each entry). Excellent, sounds like a job for SAX.
However,
Sorry, I am resending this email because I didn't write a correct title
before.
---
Greetings,
I am a Computer Science student from Argentina. I am interested in working
this summer in a project related to Haskell for the Google Summer of Code.
I have been discussing my idea with Michael
On 29/04/2013, at 3:26 AM, Chris Smith wrote:
I think it's worth backing up here, and remembering the original point
of the proposal, by thinking about what is and isn't a goal. I think
I'd classify things like this:
Goals:
- Use a lightweight, common, and familiar core syntax for simple
On Sun, Apr 28, 2013 at 6:10 PM, Richard A. O'Keefe o...@cs.otago.ac.nzwrote:
Damn! Why did Watts Humphrey have to die before he'd convinced
the world that the cheapest way to fix bugs is to keep them out
in the first place?
I think that much has to do with the historical division in
On Mon, Apr 29, 2013 at 8:42 AM, Alexander Solla alex.so...@gmail.comwrote:
I've been scoffed at during interviews for saying I solve problems on
paper before I start typing!
That has to suck. I hope you're properly avenged when you find work in a
savvier, respectful competitor and KICK THEIR
On Apr 28, 2013 6:42 PM, Alexander Solla alex.so...@gmail.com wrote:
I think that much has to do with the historical division in computer
science. We have mathematics on the right hand, and electrical engineering
on the wrong one.
I've been called many things, but electrical engineer is a new
On 29/04/2013, at 4:18 PM, Chris Smith wrote:
My point was not anything at all to do with programming. It was about
writing comments, which is fundamentally a communication activity. That
makes a difference. It's important to keep in mind that the worst possible
consequence of getting
24 matches
Mail list logo
