cubranic:
> On 2/21/06, Graham Klyne <[EMAIL PROTECTED]> wrote:
> > In making such changes, please bear in mind "Cool URIs Don't Change":
> >
> > http://www.w3.org/Provider/Style/URI
> >
> > This isn't to say "don't", but where possible, provide some redirection
> > from the
> > old name to the n
On 2/21/06, Graham Klyne <[EMAIL PROTECTED]> wrote:
> In making such changes, please bear in mind "Cool URIs Don't Change":
>
> http://www.w3.org/Provider/Style/URI
>
> This isn't to say "don't", but where possible, provide some redirection from
> the
> old name to the new name.
>
> To be effecti
On Tue, Feb 21, 2006 at 11:04:40PM +, Simon Marlow wrote:
> Your drop__ reminds me of GHC's touch#, which is like drop__ in the IO
> monad. We use it to control lifetimes, eg. inside withForeignPtr. You
> could implement drop in terms of touch#:
>
>drop__ a b = case touch# a realworld#
On Mon, Feb 20, 2006 at 10:57:23PM +, Ben Rudiak-Gould wrote:
> could static analysis then eliminate the test for FailIO in ST code? It
> would be pretty cool if the answer was yes, since it would mean that
> merging IO and ST would be an optimization instead of a pessimization (the
> test c
John Meacham wrote:
On Tue, Feb 21, 2006 at 10:15:59AM +, Malcolm Wallace wrote:
John Meacham <[EMAIL PROTECTED]> wrote:
I generalized this primitive to
drop__ :: a -> b -> b
Also known in the Prelude as "const"...
well, 'flip const' but yes.
The difference is that you propose
Am Dienstag, 21. Februar 2006 11:17 schrieb Simon Peyton-Jones:
> Sounds good to me.
>
> I wonder whether the haskell home page http://haskell.org should say
> something like
>
> "This entire site is a Wiki, and is maintained by its users. To find
> out how to contribute, go here",
>
> where "here
Am Dienstag, 21. Februar 2006 10:56 schrieb Graham Klyne:
> In making such changes, please bear in mind "Cool URIs Don't Change":
>
> http://www.w3.org/Provider/Style/URI
>
> This isn't to say "don't", but where possible, provide some redirection
> from the old name to the new name.
>
> To be eff
On Feb 20, 2006, at 5:57 PM, Ben Rudiak-Gould wrote:
John Meacham wrote:
ST doesn't have exceptions which IO does. It would be no good to
make ST
pay for the cost of exception handling. GHC handles them behind the
scenes (I think?) but in jhc they are explicit and IO is defined as
follows:
FIRST ANNOUNCEMENT and CALL FOR PAPERS
**
* 18th International Workshop on*
* Implementation and Application of Functional Languages *
*
On Tue, Feb 21, 2006 at 10:15:59AM +, Malcolm Wallace wrote:
> John Meacham <[EMAIL PROTECTED]> wrote:
>
> > I generalized this primitive to
> >
> > drop__ :: a -> b -> b
>
> Also known in the Prelude as "const"...
well, 'flip const' but yes.
> The difference is that you propose it be pri
In making such changes, please bear in mind "Cool URIs Don't Change":
http://www.w3.org/Provider/Style/URI
This isn't to say "don't", but where possible, provide some redirection from the
old name to the new name.
To be effective, the web relies on stable links, so that references from
elsewhe
Robert Dockins <[EMAIL PROTECTED]> wrote:
> On Feb 20, 2006, at 5:19 PM, [EMAIL PROTECTED] wrote:
> >
> > Data.Set, Data.Map, Data.Hash and the various Array interfaces are
> > all inconsistent in subtle ways, so whatever you do, do not take
> > them as the ideal to which Edison should aspire.
>
John Meacham <[EMAIL PROTECTED]> wrote:
> I generalized this primitive to
>
> drop__ :: a -> b -> b
Also known in the Prelude as "const"...
The difference is that you propose it be primitive, with the intention
that a clever compiler should not be able to bypass it by inlining its
definition a
Hello oleg,
Wednesday, February 08, 2006, 8:37:55 AM, you wrote:
>> I suggest you follow the same scheme as the unboxed array types, and
>> have IOURef/STURef types, parameterised over the element type. Of
>> course, we should have instances for all of the primitive numeric types
>> plus Ptr, Fo
[Apologies for multiple copies]
Preliminary Call for Papers: PPDP 2006
Eighth ACM-SIGPLAN International Symposium on
Principles and Practice of Declarative Programming
Venice, Italy, 10-12 July, 2006
IMPORTANT DATES
Submission 15 March 2
Sounds good to me.
I wonder whether the haskell home page http://haskell.org should say
something like
"This entire site is a Wiki, and is maintained by its users. To find
out how to contribute, go here",
where "here" gives guidance about logging in, and your page-naming
guidelines?
S
16 matches
Mail list logo
