Re: Re[2]: Array interface refactoring

2006-02-24 Thread Cale Gibbard
On 23/02/06, Bulat Ziganshin [EMAIL PROTECTED] wrote: Hello John, Thursday, February 23, 2006, 4:07:52 PM, you wrote: JM That is the plan. none of the current Array implementations will JM change, they will still be instances of both MArray and HasBounds. it is JM just that HasBounds will

RE: Array interface refactoring

2006-02-22 Thread Simon Peyton-Jones
| Perhaps this e-mail could be read more generally as a | request to consistencify/update the (Data) libraries | in general ... | | Is this possible for Haskell'? Or is this too much | of a break? If it's possible, I'm happy to build a | wiki page for discussion (I noticed that a short page

Re[2]: Array interface refactoring

2006-02-22 Thread Bulat Ziganshin
Hello Ben, Wednesday, February 22, 2006, 9:47:19 PM, you wrote: BRG While we're on the topic, I have a couple of problems with the current array BRG system that cut deeper than the naming: BRG * The function for getting the bounds of an MArray is pure, so the BRGinterface can't

Re: Array interface refactoring

2006-02-21 Thread Donald Bruce Stewart
alson: We had a short discussion on the IRC channel the other day about Arrays. I advocated that we do some refactoring work and didn't meet with overwhelming disagreement, so I wanted to propose that the Arrays interfaces be refactored in Haskell'. As a Haskell new-ish-bie, the various

Re: Array interface refactoring

2006-02-21 Thread Tomasz Zielonka
On Wed, Feb 22, 2006 at 03:39:48PM +1100, Donald Bruce Stewart wrote: And unsafeRead/unsafeWrite are too verbose. They are usually (almost always?) safe (since the code does its own checks), The same can be said about most uses of unsafePerformIO - you wouldn't be using it if you weren't