- Haskell-Cafe - Haskell.org

Re: [Haskell-cafe] optparse-applicative with attoparsec parser
by Sébastien Leblanc 06 Feb '22

06 Feb '22

> > Date: Fri, 4 Feb 2022 15:09:41 +0100 (CET) > From: PICCA Frederic-Emmanuel > <frederic-emmanuel.picca(a)synchrotron-soleil.fr> > To: haskell-cafe(a)haskell.org > Subject: [Haskell-cafe] optparse-applicative with attoparsec parser > Message-ID: > < > 30404406.15581346.1643983781075.JavaMail.zimbra(a)synchrotron-soleil.fr> > > Content-Type: text/plain; charset=utf-8 > > Hello, > > I Try to write a parser for this command line > > binoculars-ng --debug process data/test/config_sixs_ruche_flymedv_3.ini > 698-734 735-736 > > But I have this problem > > Invalid argument `735-736' > > The parser used for this is this one > > processOptions :: Parser Options > processOptions = Process > <$> optional config > <*> optional (argument (eitherReader (parseOnly > configRangeP . pack)) (metavar "RANGE")) > > it use the configRangeP attoparser parser whcih knows how to deal with the > string "698-734 735-736" > > configRangeP :: Parser ConfigRange > configRangeP = ConfigRange <$> (inputRangeP `sepBy` many (satisfy isSep)) > where > isSep :: Char -> Bool > isSep c = c == ' ' || c == ',' > > the result should be this one > > Just (ConfigRange [InputRangeFromTo 698 734,InputRangeFromTo 735 736]) > > so my question how should I fix my processOptions fucntion in order to > deal with this problem. > > thanks for considering > It seems that the issue stems from having your arguments separated by spaces. If your parser is parsing [[ [debug-flag] <command> <file> <ranges> ]], then it does not know what to do with the last particle (735-736). You would need to wrap your ranges in quotes in your shell, to include the space, or replace the space with a comma instead (698-734,735-736) Sébastien

1 0

Haskell Developer Roles at Standard Chartered Bank (UK and SG)
by J. Stutterheim 06 Feb '22

06 Feb '22

Hi all, I'm happy to report that my team at Standard Chartered Bank is hiring Haskell programmers! We're currently hiring in London, and we expect to open positions in Singapore soon. If you're interested in writing Haskell code for mission-critical cloud-based applications, this is the job for you. Financial knowledge is not required, as there will be plenty of opportunity to pick it up on the job. If you're interested in having a chat, please apply through the following link: https://scb.taleo.net/careersection/ex/jobdetail.ftl?job=2200001642&lang=en After applying through the link above, please shoot me an email at `jurrien dot stutterheim at sc dot com` so that I know that you have applied. Best regards, Jurriën

1 0

How can I get a list of all English words?
by Amber Crawford 06 Feb '22

06 Feb '22

I'm creating a project in which I need a list of every English word, so I'm wondering how I would get this. The only thing I need is that I can filter the words based on some boolean function, thanks. btw I'm pretty beginner so sry If i'm not really good at writing these.

6 5

optparse-applicative with attoparsec parser
by PICCA Frederic-Emmanuel 04 Feb '22

04 Feb '22

Hello, I Try to write a parser for this command line binoculars-ng --debug process data/test/config_sixs_ruche_flymedv_3.ini 698-734 735-736 But I have this problem Invalid argument `735-736' The parser used for this is this one processOptions :: Parser Options processOptions = Process <$> optional config <*> optional (argument (eitherReader (parseOnly configRangeP . pack)) (metavar "RANGE")) it use the configRangeP attoparser parser whcih knows how to deal with the string "698-734 735-736" configRangeP :: Parser ConfigRange configRangeP = ConfigRange <$> (inputRangeP `sepBy` many (satisfy isSep)) where isSep :: Char -> Bool isSep c = c == ' ' || c == ',' the result should be this one Just (ConfigRange [InputRangeFromTo 698 734,InputRangeFromTo 735 736]) so my question how should I fix my processOptions fucntion in order to deal with this problem. thanks for considering Frederic

2 1

Asking for advice on category for a paper for ICFP
by Anton Kholomiov 02 Feb '22

02 Feb '22

Hi! I'm trying to write a paper for ICFP, This is my first paper of this kind. Can you please help me to choose the right category for it? The paper is about a novel technique of implementation of FRP. I've studied the Haskell FRP zoo and I can confirm that it's novel. In my opinion it's very elegant and simple, but of course I'm biased :) So far so good. Can you please help me to choose the right category for it? Is it a normal research paper or is it a functional pearl? So the FRP is an old technique, but I propose a novel variant of implementation which I hope is easy to study even in normal class rooms and does not contain unsafePerform tricks. Cheers, Anton

5 6

[ANN] opc-xml-da-client, a client for the OPC XML-DA protocol
by Olaf Klinke 31 Jan '22

31 Jan '22

Dear Haskell Café, I am pleased to announce opc-xml-da-client [1,2], an implementation of (the client side of) the OPC XML-DA data access protocol. While the OPC XML-DA protocol is quite dated (2003) and has largely been superseded by other OPC flavours, it is still being used in industrial environments. OPC XML-DA is based on SOAP and the data types in the Haskell package closely reflect the protocol specification as a web services description language document [5]. This package was developed by Mlabs [3] as contract work for my employer. We release it as FOSS, with Mlabs kindly hosting the project under their Github account. To my knowledge, besides PyOPC [4] this is the only freely available OPC XML-DA library and the only Haskell OPC library. We stopped using PyOPC because Python hit performance limits while parsing the XML. Feel free to contact me or Nikita Volkov at Mlabs if you have further questions. Cheers Olaf [1] https://github.com/mlabs-haskell/opc-xml-da-client [2] https://hackage.haskell.org/package/opc-xml-da-client [3] https://mlabs.city [4] https://pypi.org/project/PyOPC/ [5] https://opcfoundation.org/XMLDA/1.0/OpcXmlDa1.00.wsdl

1 0

how to set extra-lib-dirs for a dependency in a stack project?
by Johannes Waldmann 30 Jan '22

30 Jan '22

Dear Cafe, is it possible to specify include-dirs and extra-lib-dirs for a dependency? I have * top-level project A, depends on: * project B, depends on: * C: external library (written in C) I am building A with stack. I don't want to put fixed locations (include/lib) for C in B.cabal, because it depends on the (top-level) build environment of A (e.g., my machine, or CI). Concrete example: C = kissat SAT solver, B = Haskell API for C. I know that, e.g., https://hackage.haskell.org/package/minisat works around this problem by vendoring (is this the word?) the solver's code (into B). I don't want this. With cabal.project, I could set options for (all?) dependencies? https://cabal.readthedocs.io/en/3.4/cabal-project.html#foreign-function-int… Would stack use this setting (will it read that file at all)? Will I have to copy all extra-deps source repo locations to cabal.project? - J.

2 3

Some Love for wxHaskell
by Tilmann 30 Jan '22

30 Jan '22

Hi cafe, I think wxHaskell needs some love :) Over the years I've written a small client for FICS (Free Internet Chess Server) and wxHaskell has served me really well. Also, wxWidgets seems solid and alive.. but today, wxHaskell is lagging behind updates and seems *sniff* dead. Is someone working on wxHaskell atm? I'd love to connect and help. If not, is there some interest to rejuvenate wxHaskell? Who is also depending on wxHaskell and wants to keep it going? Or, is it time to move on to gtk or reflex? Very much looking forward to your replies! Best, Tilmann

3 4

Coercing existential according to type-level Maybe (re-post from h-beginners)
by Dmitriy Matrosov 29 Jan '22

29 Jan '22

(as suggested, i'm re-asking here) Hi. I've tried to write a function to coerce existential value according to type stored in type-level 'Maybe' (i.e. 'Just or 'Nothing). > {-# LANGUAGE DataKinds #-} > {-# LANGUAGE RankNTypes #-} > {-# LANGUAGE KindSignatures #-} > {-# LANGUAGE PolyKinds #-} > {-# LANGUAGE TypeFamilies #-} > {-# LANGUAGE GADTs #-} > > import Data.Kind > import Data.Proxy > import Unsafe.Coerce > > class FromTypeMaybe k where > type ToType k > fromTypeMaybe :: (a -> ToType k) -> Proxy k -> a -> Maybe (ToType k) > > --instance forall (t :: Type). FromTypeMaybe ('Nothing :: Maybe t) where > instance forall (t :: Type). FromTypeMaybe ('Nothing @t) where > type ToType 'Nothing = t > fromTypeMaybe f _ x = Nothing > > instance forall (t :: Type). FromTypeMaybe ('Just t :: Maybe Type) where > type ToType ('Just t) = t > fromTypeMaybe f _ x = Just (f x) > > data Any where > Any :: a -> Any > > unAny :: Any -> t > unAny (Any x) = unsafeCoerce x This works as far as i can see *Main> fromTypeMaybe unAny (Proxy @('Just Int)) (Any 3) Just 3 *Main> fromTypeMaybe unAny (Proxy @'Nothing) undefined Nothing but i don't understand how 'Nothing instance works: type kind kind? vvv vvvvvv vvv instance forall (t :: Type). FromTypeMaybe ('Nothing :: Maybe t) where type ToType 'Nothing = t ^^^ type (in case alignment breaks: variable 't' in forall is type-variable with kind 'Type', but in "Maybe t" in instance head it's used as kind-variable. And then in associated type-family the same variable 't' is used as type-variable again). If i try to write "'Nothing"'s kind as 'Maybe Type' (in the same manner as 'Just has) instance forall (t :: Type). FromTypeMaybe ('Nothing :: Maybe Type) where i get an error: 1.lhs:21:3: error: • Type variable ‘t’ is mentioned in the RHS, but not bound on the LHS of the family instance • In the type instance declaration for ‘ToType’ In the instance declaration for ‘FromTypeMaybe ('Nothing :: Maybe Type)’ | 21 | > instance forall (t :: Type). FromTypeMaybe ('Nothing :: Maybe Type) where | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^... Well, i'm not sure, that understand why 'forall' in instance head may not be used as family's LHS, but.. that's another question. On the other hand, if i try to write 'Just instance using type-variable 't' as kind-variable (in the same manner as 'Nothing has): instance forall (t :: Type). FromTypeMaybe ('Just t :: Maybe t) where i get an error too: 1.lhs:25:47: error: • Expected kind ‘Maybe t’, but ‘'Just t’ has kind ‘Maybe *’ • In the first argument of ‘FromTypeMaybe’, namely ‘('Just t :: Maybe t)’ In the instance declaration for ‘FromTypeMaybe ('Just t :: Maybe t)’ | 25 | > instance forall (t :: Type). FromTypeMaybe ('Just t :: Maybe t) where Well, that's also probably expected, because though i've declared type-variable 't' with kind 'Type' in forall, due to 'DataKinds' extension type 't' is also promoted to kind 't' and, thus, by using ('Just t :: Maybe t) i say, that ('Just t) should have kind 'Maybe t', not 'Maybe Type', which it really has. But if that's so, how working 'Nothing instance instance forall (t :: Type). FromTypeMaybe ('Nothing :: Maybe t) where may work at all? It has the same problem as 'Just instance above: type-variable 't' is promoted to kind 't' and 'Nothing will have kind 'Maybe t' instead of 'Maybe Type' ?

3 10

Request for Nominations to the GHC Steering Committee
by Joachim Breitner 29 Jan '22

29 Jan '22

Dear Haskell community, the GHC Steering committee is seeking nominations for at least two new members. The committee scrutinizes, nitpicks, improves, weights and eventually accepts or rejects proposals that extend or change the language supported by GHC and other (public-facing) aspects of GHC. Our processes are described at https://github.com/ghc-proposals/ghc-proposals which is also the GitHub repository where proposals are proposed. In particular, please have a look at the bylaws at https://github.com/ghc-proposals/ghc-proposals/blob/master/committee.rst We are looking for a member who has the ability * to understand such language extension proposals, * to find holes and missing corner cases in the specifications, * foresee the interaction with other language features and specifications, * comment constructively and improve the proposals, * judge the cost/benefit ratio and * finally come to a justifiable conclusion. We look for committee members who have some of these properties: * have substantial experience in writing Haskell applications or libraries, which they can use to inform judgements about the utility or otherwise of proposed features, * have made active contributions to the Haskell community, for some time, * have expertise in language design and implementation, in either Haskell or related languages, which they can share with us. The committee’s work requires a small, but non-trivial amount of time, especially when you are assigned a proposal for shepherding. We estimate the workload to be around 2 hours per week, and our process works best if members usually respond to technical emails within 1-2 weeks (within days is even better). Please keep that in mind if your email inbox is already overflowing. There is no shortage of people who are eager to get fancy new features into the language, both in the committee and the wider community. But each new feature imposes a cost, to implement, to learn, (particularly) through its unexpected interaction with other features. We need to strike a balance, one that encourages innovation (as GHC always has) while still making Haskell attractive for real-world production use and for teaching. We therefore explicitly invite “conservative” members of the community to join the committee. To make a nomination, please send an email to me (as the committee secretary) at mail(a)joachim-breitner.de until February 11th. I will distribute the nominations among the committee, and we will keep the nominations and our deliberations private. We explicitly encourage self-nominations. You can nominate others, but please obtain their explicit consent to do so. (We don’t want to choose someone who turns out to be unable to serve.) On behalf of the committee, Joachim Breitner -- Joachim Breitner mail(a)joachim-breitner.de http://www.joachim-breitner.de/

1 0