Haskell definitely takes the cake in terms of leveraging parser combinators, but...

wesselbindt · 2024-11-08T07:30:40 1731051040

That's what they call a "win-win".

pjmlp · 2024-11-08T07:22:02 1731050522

For some of us, "being stuck with Haskell" isn't a problem.

anilakar · 2024-11-08T08:15:09 1731053709

For the rest, being stuck with real-world problems instead of self-inflicted ones is preferable :-)

pjmlp · 2024-11-08T11:55:26 1731066926

Doesn't seems so, otherwise the computing world wouldn't be so full of NIH syndrome. :)

instig007 · 2024-11-08T10:02:35 1731060155

re-inventing known language features in inferior languages isn't more real-world, it's a self-inflicting kool-aid thirst ^_^

HKH2 · 2024-11-08T11:02:58 1731063778

Has Cabal been fixed yet?

kreetx · 2024-11-08T14:45:39 1731077139

Yes, a long time ago [0]. Depending on your needs, stack might still have advantages as the direct tool used by the developer (as it uses cabal underneath anyway).

[0] https://stackoverflow.com/a/51016806/4126514

instig007 · 2024-11-08T14:46:28 1731077188

At least since August 2017: https://downloads.haskell.org/~cabal/Cabal-3.0.0.0/doc/users...

You don't need switching to Stack (as other commenters suggest) to have isolated builds and project sandboxes etc. If you want to bootstrap a specific compiler version, a-la nvm/pyenv/opam, use GHCup with Cabal project setup: https://www.haskell.org/ghcup/

ryandv · 2024-11-08T14:31:45 1731076305

Yes. Use stack [0].

[0] https://docs.haskellstack.org/en/stable/

PittleyDunkin · 2024-11-08T15:53:48 1731081228

I like haskell a lot, but it's not like there's any shortage of reasons why people don't use it. Replicating parser-combinators in other languages is a huge win.

zxexz · 2024-11-08T08:54:43 1731056083

As someone who really enjoys Haskell, I used to think like that. But I realized for problems like parsing, it really is just excellent.

instig007 · 2024-11-08T06:41:10 1731048070

don't make it sound as if it's bad, it's actually superb on all these levels: the typelevel, the SMP runtime, and throughput.

fuzztester · 2024-11-08T07:31:51 1731051111

$ echo "Haskell" | sed 's/ke/-ki'

Has-kill

$

fuzztester · 2024-11-08T07:34:53 1731051293

| sed '/k/sk'

Has-skill

$

orf · 2024-11-08T08:16:06 1731053766

Write the full transform in Haskell?

itishappy · 2024-11-08T14:32:44 1731076364

    {-# LANGUAGE OverloadedStrings #-}

    import Prelude hiding (putStrLn)
    import Data.Text (Text, replace)
    import Data.Text.IO (putStrLn)

    transform :: Text -> Text
    transform = replace "k" "sk" . replace "ke" "-ki" 

    main :: IO ()
    main = putStrLn $ transform "Haskell"

sshine · 2024-11-11T02:25:17 1731291917

Since the original sed command took "Haskell" as standard input, why not:

  {-# LANGUAGE OverloadedStrings #-}

  import qualified Data.Text as T
  import qualified Data.Text.IO as T

  main :: IO ()
  main = T.interact (T.replace "k" "sk" . T.replace "ke" "-ki")

itishappy · 2024-11-11T15:01:36 1731337296

Didn't think to, but that looks very slick!

fuzztester · 2024-11-10T01:49:12 1731203352

Looks good to me, even as a Haskell ignoramus. I had tried it long back, but found it tough at the time.

What is the reason for hiding the putStrLn of Prelude and importing that of Data.Text.IO?

itishappy · 2024-11-10T05:41:37 1731217297

Prelude takes a `String`, Data.Text.IO works with `Text`. Strings are linked lists of of chars, Text is a more traditional data structure. I tend to write small scripts and use Strings more, but Text is much more efficient for big blocks of text (unsurprisingly). The main reason I used it here was because I couldn't find a `replace` function for `String`, lol.

fuzztester · 2024-11-10T17:41:03 1731260463

Thanks.

mkl · 2024-11-08T10:30:20 1731061820

  sed: -e expression #1, char 5: unterminated `s' command

It's like this:

  sed 's/find/replace/'

fuzztester · 2024-11-08T14:18:16 1731075496

Whoops, it was a typo. I do know how to use the sed command, at least the basics; see my previous use of it ( https://news.ycombinator.com/item?id=42084984 ). But thanks, good catch.

fuzztester · 2024-11-08T23:25:25 1731108325

HN "bros" (in the ugliest sense of the word "bro") showing their sick nature by viciously downvoting a perfectly innocuous comment.

Seems like many of them have nothing better to do, probably because of layoffs and statistics and linear algebra and 'predicting the next token' (hee hee) in the input, based on gigantic corpuses of data, masquerading as "AI", and many of those bros were/are worthless anyway.