Another option: use cabal-dev with --enable-library-profiling. It should do
the trick.
Best regards,
Krzysztof Skrzętnicki
On Wed, Apr 17, 2013 at 11:13 PM, Anatoly Yakovenko
wrote:
>
>
> ___
> Haskell-Cafe mailing list
> Haskell-Cafe@haskell.org
> ht
You are right Alejandro, arrows are a perfect fit here. (Most of it
is possible with monads as well, but arrows are useful to maintain
static names of the properties.)
Here's what I've come up with: https://gist.github.com/feuerbach/5409326
Now everyItem and hasJust have types
everyItem :: Mat
==
FARM 2013: Call for Papers
ACM SIGPLAN Workshop on Functional Art, Music, Modeling and Design
Boston, Massachusetts, USA
28th September, 2013 (directly after ICFP)
* Stephen Tetley [2013-04-16 19:48:47+0100]
> On 16 April 2013 16:12, Alejandro Serrano Mena wrote:
> > Hi,
> > First of all, let me say that this work on matchers is really useful :)
> >
> > Following Roman advice, I'm trying to find a more principled approach
> > that could be useful for this l
Hi all,
I'd like to announce a hopefully useful new package: algebraic-classes. In
short it provides conversions between algebraic classes and F-algebras, which
should make generating instances of certain classes easier.
Algebraic classes are classes where every method has the same result type,
My "simple" way is to move ~/.ghc (or ~/.ghc and ~/.cabal) somewhere else,
then make (e.g. by running cabal update) or edit ~/.cabal/config to say
library profiling, executable profiling and documentation: True, then run
cabal install on one of my projects.
On Wed, Apr 17, 2013 at 5:13 PM, Anat
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
Yesod was already in round two which happened the next day:
http://www.techempower.com/blog/2013/04/05/frameworks-round-2
I have seen a mention of a round 4 planned(on google+?), but have not seen
the results for round 3.
Patrick
On Wednesday, April 17, 2013 9:35:14 AM UTC-5, Jeffrey Shaw wrot
True, and thank you for clarifying that. I was thinking of the names of the
field data, not the type-level name of the field:
name = Field :: "name" ::: String
-IRS
From: acow...@gmail.com [acow...@gmail.com] on behalf of Anthony Cowley
[acow...@seas.upe
For better or worse; IEEE-754 settled many of these questions.
I personally think the standard is a good compromise of what's practical,
efficiently implementable, and mathematically sensible. I find the
following paper by Rummer and Wahl an especially good read:
http://www.ccs.neu.edu/
On 4/14/13 8:53 PM, Kim-Ee Yeoh wrote:
> On Sun, Apr 14, 2013 at 3:28 PM, wren ng thornton
wrote:
>> Whereas the problematic
>> values due to infinities are overspecified, so no matter which answer you
>> pick it's guaranteed to be the wrong answer half the time.
>>
>> Part of this whole problem c
Somebody already added snap:
https://github.com/TechEmpower/FrameworkBenchmarks/tree/master/snap.
On Wed, Apr 17, 2013 at 2:35 PM, Jeffrey Shaw wrote:
> I was excited to see if Warp or Snap was included, but I was sad to see they
> weren't. If I find time someday, I'll add benchmarks for them, bu
On Apr 17, 2013, at 8:05 AM, Andres Löh wrote:
> Changes in version 0.10
>
> * NFData instances
> "
thanks :).
Anatoly
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
Hi again.
> instance NFData (V.Vector a) where rnf a = force a `seq` ()
>
>
> any reason why something like this isn't part of the vector library?
Quoting from the Changelog at http://hackage.haskell.org/package/vector :
"
Changes in version 0.10
* NFData instances
"
So it's there, and eve
so this one works
instance NFData (V.Vector a) where rnf a = force a `seq` ()
any reason why something like this isn't part of the vector library?
Thanks,
Anatoly
On Apr 17, 2013, at 7:51 AM, anatoly yakovenko wrote:
> Thanks, So now i at least get a compiler error
>
>No instance fo
Thanks, So now i at least get a compiler error
No instance for (NFData (V.Vector Double))
So how would one define NFData instance for vector?
On Apr 16, 2013, at 10:51 PM, Andres Löh wrote:
>> NFData Simple where rnf = genericRnf
___
Haskell-
I was excited to see if Warp or Snap was included, but I was sad to see
they weren't. If I find time someday, I'll add benchmarks for them, but it
will be a long time. If anyone else wants to take a stab at it, that'd be
awesome!
http://www.techempower.com/blog/2013/03/28/framework-benchmarks/
Je
>> ghc is installed globally, and local packages should not "break" it.
>
> still cabal-install says so (and I don't dare to test ...)
If you're installing locally or (even better) in a sandbox, then you
cannot completely (i.e., irrevocably) break your compiler. You can
always remove the package d
Roman Cheplyaka ro-che.info> writes:
> On second thought, are you trying to install it globally?
locally
> ghc is installed globally, and local packages should not "break" it.
still cabal-install says so (and I don't dare to test ...)
___
Haskel
I'm pleased to announce Blip version 0.1.0, a bytecode compiler for Python
3.
https://github.com/bjpop/blip
Blip compiles Python 3 source files to bytecode. The output bytecode is
compatible with the CPython interpreter (the "standard" Python
implementation).
For example, given a Python 3 so
On second thought, are you trying to install it globally?
ghc is installed globally, and local packages should not "break" it.
* Johannes Waldmann [2013-04-17 08:36:23+]
> Roman Cheplyaka ro-che.info> writes:
>
> > ghc is the package that provides the GHC API.
> > Breaking it should not a
Warning: no knowledge of Yampa.
It seems that the integration for the position is always using the velocity
from the previous step. Looking at the documentation in source code of
Yampa this seems plausible as there is also a function called imIntegrate
with the comment
-- "immediate" integration
Roman Cheplyaka ro-che.info> writes:
> ghc is the package that provides the GHC API.
> Breaking it should not affect the compiler itself, since it is
> statically linked.
Yes. But once ghc (the package) is broken,
it cannot be fixed (except by re-installing ghc (the compiler))?
_
* Johannes Waldmann [2013-04-17 08:10:21+]
> (Isn't it somewhat bold of cabal-install to offer to break "ghc-7.6.2"?
> like, this will completely hose the compiler?)
ghc is the package that provides the GHC API.
Breaking it should not affect the compiler itself, since it is
statically linked.
On 17 April 2013 18:10, Johannes Waldmann wrote:
> Is it still the case that
> "It just doesn't work to have multiple versions of a wired-in package"
> (cf. http://hackage.haskell.org/trac/ghc/ticket/5704 )?
>
> ghc-7.6.2 comes with containers-0.5.0.0 and template-haskell-2.8.0.0 .
> It seems I ca
Is it still the case that
"It just doesn't work to have multiple versions of a wired-in package"
(cf. http://hackage.haskell.org/trac/ghc/ticket/5704 )?
ghc-7.6.2 comes with containers-0.5.0.0 and template-haskell-2.8.0.0 .
It seems I can upgrade to containers-0.5.2.1 and use it with no problems
26 matches
Mail list logo
