roberth

#!./interpret.nix

{ io, args, ... }:

let
  main =
    io.printLine "I'm hi, who are you?" ask;

  ask = 
    io.readLine (name:

roberth

{-# LANGUAGE DerivingStrategies #-}
{-# LANGUAGE ExistentialQuantification #-}
{-# LANGUAGE GeneralizedNewtypeDeriving #-}
{-# LANGUAGE PatternSynonyms #-}
{-# LANGUAGE RankNTypes #-}
{-# LANGUAGE ViewPatterns #-}
{-# LANGUAGE ExplicitNamespaces #-}
{-# LANGUAGE TypeOperators #-}

-- |  An alternate implementation of the Ghosts of Departed Proofs <https://kataskeue.com/gdp.pdf idea>,

roberth

Why no 👎 reaction?

The main problem with the 👎 reaction is that it does not carry any constructive feedback or explanation.

In some cases, it is added to a pull request early on, before the author has had a chance to improve their proposal. The person placing the reaction often will not receive a notification of the improvements and even if they did, they may forget to remove the 👎.

These effects are not obvious to the author or the person reacting; let alone to the reader. This causes friction for everyone involved.

But I don't want to add noise!

roberth

{-# LANGUAGE DerivingStrategies #-}
{-# LANGUAGE DerivingVia #-}
{-# LANGUAGE ExistentialQuantification #-}
{-# LANGUAGE GeneralizedNewtypeDeriving #-}
{-# LANGUAGE StandaloneDeriving #-}


-- | This is a strict, somewhat efficient implementation of something between 'Data.List.partition' and Beautiful Folding.
--
-- It allows a (pure or ST) stream of values to be processed into multiple fields, using a nice 'Applicative' interface.

roberth

{-# LANGUAGE GADTs #-}
{-# LANGUAGE GeneralizedNewtypeDeriving #-}

module Hasql.Extras.QueryPart where

import Data.Functor.Compose
import Data.String (IsString (..))
import qualified Hasql.Decoders as HD
import qualified Hasql.Encoders as HE
import qualified Hasql.Statement as HQ

roberth

/*
  minimod: A stripped down module system

  TODO Comparison:
    - [ ] Come up with a benchmark "logic" using plain old functions and let bindings
    - [ ] Write the benchmark for the module system
    - [ ] Write the benchmark for POP?
    - [ ] Qualitative comparison of extensibility in the context of composable
          Nixpkgs packaging logic
  TODO Fine-tuning:

roberth

NOTE: this is a draft

TODO comments are in the source

This spec must be validated by implementing it in at least one library. I may do this in Haskell's optparse-applicative.

---