Thanks for pointing to "type level integers". With that I have found:
http://www.haskell.org/haskellwiki/The_Monad.Reader/Issue5/Number_Param_Types
For example:
---
data Zero = Zero
data Succ a = Succ a
class Card c where
c2num:: c -> Integer
cpred::(Succ c)
I should add that as a consumer of Haddock documentation
I can testify that fancier styling (in whatever format)
would be of little benefit to _me_. What I need is more
plain text and more examples.
To be perfectly honest, most of the time when looking at
a Haddock page, I end up clicking on the
I would like to propose the development of source code refactoring tool
that operates on Haskell source code ASTs and lets you formulate rewrite
rules written in Haskell.
Objective
-
The goal is to make refactorings easier and allow global code changes
that might be incredibly tedious to
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 get
On Apr 28, 2013 6:42 PM, "Alexander Solla" 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 one!
My point was
On Mon, Apr 29, 2013 at 8:42 AM, Alexander Solla wrote:
> 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 ASSES!
-- Kim-Ee
On Sun, Apr 28, 2013 at 6:10 PM, Richard A. O'Keefe wrote:
>
> 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 computer
science. We
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 s
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 Snoy
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, afte
On Sun, Apr 28, 2013 at 10:55 AM, gs wrote:
> Alexander Solla 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 poo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/04/13 18:37, Marcos Pividori wrote:
> 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 Mi
Alexander Solla 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
orientated forum :-
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 GH
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
On Sun, Apr 28, 2013 at 10:29 AM, gs wrote:
> Brandon Allbery 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 p
Brandon Allbery 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 compilers,
an
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
On Sun, Apr 28, 2013 at 3:59 AM, harry wrote:
> Dan Doel 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 t
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 can'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/04/13 11:57, Joe Nash wrote:
> On 28 Apr 2013 11:33, "Mateusz Kowalczyk"
> wrote:
>>>
>>> If the flexibility of having it pandoc compatible is a desired
>>> feature, can this not be achieved through implementing markdown
>>> for haddock as wel
On 28 Apr 2013 11:33, "Mateusz Kowalczyk" 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 popular sy
-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 e
> Aleksandar Dimitrov 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 in OOHaskel
On Sat, 27 Apr 2013 22:56:32 +0200, John MacFarlane
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 my very limited Win
Dan Doel 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 won't conf
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 critica
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
28 matches
Mail list logo