- Haskell-Cafe - Haskell.org

haskell in the cloud
by Dennis Raddle 24 May '18

24 May '18

I have a CPU-intensive Haskell application. I have it working with simple multi-core concurrency. I'm wondering if I can run this on a cloud virtual machine with 128 cores or so, paying by the CPU minute. I'll run it for maybe 15 minutes a day so I'm probably best off paying just for the CPU used. What platform would be recommended? For ease of use? For best price/performance? It's a backtracking optimization algorithm that builds data, one element at a time. It's not hard at all to make it concurrent: at the first 3 or so levels of element choices would be about 100 to 500 combinations. Even if the simplest method of running concurrent Haskell on multiple cores doesn't work, I could just divide these first cases into batches and run them on individual machines. D

7 8

how do cabal internal libraries work?
by Evan Laforge 24 May '18

24 May '18

The example at https://www.haskell.org/cabal/users-guide/developing-packages.html#library doesn't seem to work as I expect. The doc for the library field is out of date, but if you scroll down it mentions "internal libraries". But depending on the internal library doesn't seem to have any effect, in that cabal still complains I didn't mention Foo.Internal, and doesn't see the build-depends from it. Am I misinterpreting how the feature is supposed to work? This is with Cabal 2.2.0.1 and cabal-install 2.2.0.0, ghc 8.4.1: % cat testing.cabal name: foo version: 1.0 license: BSD3 cabal-version: >= 1.23 build-type: Simple library foo-internal exposed-modules: Foo.Internal build-depends: base, text library exposed-modules: Foo.Public build-depends: foo-internal, base % cat Foo/Internal.hs module Foo.Internal where import Data.Text % cat Foo/Public.hs module Foo.Public where import Foo.Internal % cabal build Resolving dependencies... Configuring foo-1.0... Warning: Packages using 'cabal-version: >= 1.10' must specify the 'default-language' field for each component (e.g. Haskell98 or Haskell2010). If a component uses different languages in different modules then list the other ones in the 'other-languages' field. Preprocessing library 'foo-internal' for foo-1.0.. Building library 'foo-internal' for foo-1.0.. [1 of 1] Compiling Foo.Internal ( Foo/Internal.hs, dist/build/foo-internal/Foo/Internal.o ) [1 of 1] Compiling Foo.Internal ( Foo/Internal.hs, dist/build/foo-internal/Foo/Internal.p_o ) Preprocessing library for foo-1.0.. Building library for foo-1.0.. <no location info>: warning: [-Wmissing-home-modules] These modules are needed for compilation but not listed in your .cabal file's other-modules: Foo.Internal [1 of 2] Compiling Foo.Internal ( Foo/Internal.hs, dist/build/Foo/Internal.o ) Foo/Internal.hs:2:1: error: Could not find module ‘Data.Text’ Use -v to see a list of the files searched for. | 2 | import Data.Text | ^^^^^^^^^^^^^^^^

3 3

profunctorial vs vanlaarhoven lenses
by Paolino 23 May '18

23 May '18

Hello, I'm trying to write a lens for a datatype which seems easy in the Twan van Laarhoven encoding but I cannot find it as easy in the profunctorial one data Q5 a b = Q51 a (Identity b) | Q52 [b] lq5Twan :: Applicative f => (b -> f b') -> Q5 a b -> f (Q5 a b') lq5Twan f (Q51 a bs) = Q51 a <$> traverse f bs lq5Twan f (Q52 bs) = Q52 <$> traverse f bs data BT tt tt' b t t' a = BT1 (tt -> b) (t a) | BT2 (tt' -> b) (t' a) deriving (Functor,Foldable,Traversable) runBT (BT1 f x) = f x runBT (BT2 f x) = f x lq5Profunctor :: forall p a b b' . Traversing p => p b b' -> p (Q5 a b) (Q5 a b') lq5Profunctor = dimap pre post . second' . traverse' where pre (Q51 a x) = ((), BT1 (Q51 a) x) pre (Q52 bs) = ((), BT2 Q52 bs) post ((),x) = runBT x The issue here is that I need to project type 'b' into 2 different Traversable (sketched [] and Identity) so the traverse' must handle both together. Is the lq5Twan correct ? Which simpler ways to write the lq5Profunctor we have ? Thanks for help. paolino

3 8

Question of defining Type Class
by Shinichi Higashino 22 May '18

22 May '18

I am confusing since I am trying to define Abstract sense of Matrix; class Mat - is a more abstract concept since 1x1 Matrix is isomorphic to Num - is a more abstract concept since 1xn Matrix is isomorphic to Vector So, class Mat a => Num a where … class Mat a => Vec a where … should be . However, I know that the Initial object of Ring Category is Integer . So, I should start with Z and then I should define class ( Module R on Z ) But I could not find that kind of definition in Haskell. Is it Data.Ring ? I am so confusing now… Please help me if you are drinking some tea just now!

1 1

Tezos is hiring 40 functional programmers
by Ryan Trinkle 21 May '18

21 May '18

Hi everyone, I received this from Tezos - one of Obsidian's clients - and I thought it would be of interest to people here. Tezos is a blockchain and a platform of distributed applications written in OCaml, which brings scalability, formal verification and self-amendment to the blockchain space. Tezos has 40 open positions in the world including 25 in France. Remote and part-time accepted. We are looking for profiles ranging from masters (with possible funding for PhD) to PhD with extensive experience. Expertise in a functional language such as OCaml, Haskell, Clojure or equivalent is required, as well as skills in one of the following topics: algorithms, compilers, design of programming languages, cryptography, p2p, web programming / UI in OCaml, SAT / SMT, linear and integer programming, formal verification, stochastic processes, computer algebra or numerical optimization. Highly competitive salaries. If you are interested, please send your CV (resumé) to careers(a)tezos.com Best, Ryan

1 0

tutorials, Freer or "data a la carte"
by Dennis Raddle 21 May '18

21 May '18

I'm interested in Control.Monad.Freer, but I would need some kind of tutorial aimed at a low-intermediate level. Also I think "data a la carte" might be applicable to me, but again I would need some kind of tutorial. D

2 1

Archival of community.haskell.org
by Mario Rogic 19 May '18

19 May '18

Hi all As announced back in 2015 <http://blog.haskell.org/post/7/the_future_of_community.haskell.org/> we have started archiving community.haskell.org services. We've created https://archives.haskell.org/, and the old projects mailing lists have been the first to be archived. Next on the list is the remainder of projects.haskell.org, and the code.haskell.org site. As always, you can email admin@h.o or hop on the #haskell-infrastructure freenode channel to provide feedback / concerns. Thanks - Mario

1 2

typeclasses considered unnecessary/the power of the @
by Anthony Clayden 18 May '18

18 May '18

Haskell 98/2010 keeps a strict distinction between term-level syntax and tokens vs type-level. With ExplicitTypeApplications that's being eased: there's a lightweight way to sneak a type expression into a term. And ghc's internal term language 'core' has had explicit type applications for many years. Then consider a lightweight syntax using type applications in patterns to define typeclass instances by (pattern) 'matching' on types: > (==) @Int x y = primEqInt x y -- or eta-reduced > (==) @Int = primEqInt -- shorthand for > > instance Eq Int where > (==) = primEqInt Given that many typeclasses have a single method (or one base method with others defined in terms of it) [Note **], having to invent a typeclass name is a bit of a pain. Here's a lighweight method decl: > meth :: @a @b. => a -> b -> Bool -- typevar binding to left of => (there might also be superclass constraints) > -- shorthand for > > class Classfor_meth a b where -- generated class name > meth :: a -> b -> Bool Do we need class names at all? We could sneak term-level names into types. Just use the method name in constraints (with some handy syntactic marking -- what could be better than prefix @): > meth2 :: (@meth a b, @show b) => a -> b -> String > meth2 x y = if (meth x y) then show y else "blah" Of course we can infer the constraints on `meth2`, given its equation. Note **: for some of the Prelude's classes with many methods, like Num, there's long-standing complaints that the methods are too much tangled up and should be refactored into a hierarchy with a single method in each class: Additive, Multiplicative, Divisive, etc. With type families we can tackle the classic collections class (with methods empty, insert) as a superclass constraint , er, supermethod method: > type family Elem c :: * > insert @c. => c -> Elem c -> c > > empty :: @c. (@insert c) => c -- entangle empty with insert Likewise for Monad: > (>>=) :: @m. => (m a) -> (a -> m b) -> (m b) > > return :: @m. (@>>= m) => a -> m a The soon-to-arrive Quantified Constraints extension will provide further ways to entangle methods/constraints. That might be an alternative way to express collections: > insert @c @e. (e ~ Elem c) => c -> e -> c > > empty @c. (forall e. @insert c e => @empty c) => c Of course all the above syntax is speculative/bikesheddable. The syntax needs to differentiate tyvars that are parameters/overloadable to the class/method vs parametric free tyvars. With explicit forall: > (>>=) :: forall m a b. @m. => (m a) -> (a -> m b) -> (m b) > > return :: forall m a. @m. (@>>= m) => a -> m a Or perhaps method signatures should look more like methods-as-constraints -- at cost of a bit of repetition > (>>=) :: forall m a b. (@>>= m) => (m a) -> (a -> m b) -> (m b) > > return :: forall m a. (@return m, @>>= m) => a -> m a AntC

3 3

compilation error of tensorflow-proto 0.1.0.0
by Fabien R 18 May '18

18 May '18

Hello, Using ghc 8.2.2 (debian) , I got the following error while building the package with cabal 2.0: Building library for tensorflow-proto-0.1.0.0.. creating dist/build /media/travail/ghc/bin/ghc --make -fbuilding-cabal-package -O -static -dynamic-too -dynosuf dyn_o -dynhisuf dyn_hi -outputdir dist/build -odir dist/build -hidir dist/build -stubdir dist/build -i -idist/build -i. -idist/build/autogen -idist/build/global-autogen -Idist/build/autogen -Idist/build/global-autogen -Idist/build -I. -optP-include -optPdist/build/autogen/cabal_macros.h -this-unit-id tensorflow-proto-0.1.0.0-A707TW4oXcjUPzDlNSl3T -hide-all-packages -Wmissing-home-modules -package-db dist/package.conf.inplace -package-id proto-lens-0.2.2.0-4VJbI6HHabd74gTwpFhCiY -package-id proto-lens-protoc-0.2.2.3-KiMlOomTiwkJiIiDqOmBdc -package-id base-4.10.1.0 -XHaskell2010 Proto.Tensorflow.Core.Framework.AttrValue Proto.Tensorflow.Core.Framework.Graph Proto.Tensorflow.Core.Framework.NodeDef Proto.Tensorflow.Core.Framework.OpDef Proto.Tensorflow.Core.Framework.ResourceHandle Proto.Tensorflow.Core.Framework.Summary Proto.Tensorflow.Core.Framework.Tensor Proto.Tensorflow.Core.Framework.TensorShape Proto.Tensorflow.Core.Framework.Types Proto.Tensorflow.Core.Protobuf.Config Proto.Tensorflow.Core.Util.Event Proto.Tensorflow.Core.Framework.AllocationDescription Proto.Tensorflow.Core.Framework.CostGraph Proto.Tensorflow.Core.Framework.Function Proto.Tensorflow.Core.Framework.StepStats Proto.Tensorflow.Core.Framework.TensorDescription Proto.Tensorflow.Core.Framework.Versions Proto.Tensorflow.Core.Protobuf.Debug [ 1 of 18] Compiling Proto.Tensorflow.Core.Framework.AllocationDescription ( dist/build/autogen/Proto/Tensorflow/Core/Framework/AllocationDescription.hs, dist/build/Proto/Tensorflow/Core/Framework/AllocationDescription.o ) dist/build/autogen/Proto/Tensorflow/Core/Framework/AllocationDescription.hs:159:15: error: â¢ Couldn't match expected type âData.ProtoLens.MessageDescriptor AllocationDescriptionâ with actual type âData.Map.Map Prelude.String (Data.ProtoLens.FieldDescriptor AllocationDescription) -> Data.ProtoLens.MessageDescriptor AllocationDescriptionâ â¢ Probable cause: âData.ProtoLens.MessageDescriptorâ is applied to too few arguments In the expression: Data.ProtoLens.MessageDescriptor (Data.Map.fromList [(Data.ProtoLens.Tag 1, requestedBytes__field_descriptor), (Data.ProtoLens.Tag 2, allocatedBytes__field_descriptor), (Data.ProtoLens.Tag 3, allocatorName__field_descriptor), (Data.ProtoLens.Tag 4, allocationId__field_descriptor), ....]) (Data.Map.fromList [("requested_bytes", requestedBytes__field_descriptor), ("allocated_bytes", allocatedBytes__field_descriptor), ("allocator_name", allocatorName__field_descriptor), ("allocation_id", allocationId__field_descriptor), ....]) Does it mean that I have the wrong version of proto-lens ? * proto-lens Synopsis: A lens-based implementation of protocol buffers in Haskell. Default available version: 0.3.1.0 Installed versions: 0.2.2.0, 0.3.1.0 Homepage: https://github.com/google/proto-lens#readme License: BSD3 -- Fabien

4 6

2nd CfP Workshop on Functional High-Performance Computing 2018
by Kei Davis 17 May '18

17 May '18

2nd CfP Workshop on Functional High-Performance Computing 2018 The 7th ACM SIGPLAN Workshop on Functional High-Performance Computing (FHPC 2018) is being held as in previous years in conjunction with the International Conference on Functional Programming (ICFP 2018) together with numerous other workshops/symposia, and as a first, colocated with Strange Loop, in St. Louis, MO, USA. https://icfp18.sigplan.org/track/FHPC-2018-papers#FHPC-2018-Call-for-Papers -- Kei Davis Applied Computer Science Group CCS-7, Mail Stop B287 Los Alamos National Laboratory Los Alamos, NM 87545, U.S.A.

1 0