etorreborre

ssh-keygen -t rsa -b 4096 -N '' -C "rthijssen@gmail.com" -f ~/.ssh/id_rsa
ssh-keygen -t rsa -b 4096 -N '' -C "rthijssen@gmail.com" -f ~/.ssh/github_rsa
ssh-keygen -t rsa -b 4096 -N '' -C "rthijssen@gmail.com" -f ~/.ssh/mozilla_rsa

etorreborre

module ConcurrentMap where

import Control.Concurrent.STM.TVar (TVar)
import Control.Concurrent.STM (STM)
import Data.Hashable (Hashable)
import Data.HashMap.Strict (HashMap)
import Data.Vector (Vector)

import qualified Control.Concurrent.STM.TVar as TVar
import qualified Data.Hashable               as Hashable

etorreborre

{-# LANGUAGE BlockArguments #-}
{-# LANGUAGE DerivingVia #-}
{-# LANGUAGE FlexibleInstances #-}
{-# LANGUAGE GeneralizedNewtypeDeriving #-}
{-# LANGUAGE InstanceSigs #-}
{-# LANGUAGE PostfixOperators #-}
{-# LANGUAGE RankNTypes #-}
{-# LANGUAGE ScopedTypeVariables #-}
{-# LANGUAGE UndecidableInstances #-}
{-# LANGUAGE TypeApplications #-}

etorreborre

Pull request #8373 implementing issue 333 (but please note differences).

Pull request description follows:

This PR adds a -Wconf compiler flag that allows filtering and configuring compiler warnings (silence them, or turn them into errors).

It also integrates the fantastic silencer compiler plugin by @ghik into the compiler, which allows suppressing warnings locally using the @nowarn annotation.

etorreborre

Hi Eric,

https://twitter.com/leashless/status/1002715630536151041 "We are going to need to be much, much smarter about this blockchain thing. It's not clear to people that we are building tools to manage scarce planetary resources through the difficult 21st century. They think it's just an extension of the current economy. That can't be true."

RChain Background from Actors to Rho Calculus to Blockchain

etorreborre

{-# LANGUAGE TypeOperators #-}
import           Control.Applicative
import           Data.Extensible
import           Control.Monad.Trans.Maybe
import           Data.Text

-- the shape of the problem
--
-- we want a list of Parsers, all of different types.
-- we will apply each of them, one after another,

etorreborre

module Parser where

import Control.Applicative
-- this is from the extensible package
import Data.Extensible.HList
import Data.Text

-- the shape of the problem
--
-- we want a list of Parsers, all of different types.

etorreborre

The Problem

Defining records in Haskell causes accessor functions for the record's fields to be defined. There is no seperate namespace for these accessor functions.

The Goal

Be able to

• use records in Haskell, which share field names.
• use lenses for accessing these fields

etorreborre

The question of "How do I design my application in Haskell?" comes up a lot. There's a bunch of perspectives and choices, so it makes sense that it's difficult to choose just one. Do I use plain monad transformers, mtl, just pass the parameters manually and use IO for everything, the ReaderT design pattern, free monads, freer monads, some other kind of algebraic effect system?!

The answer is: why not both/all?

Lately, I've been centering on a n application design architecture with roughly three layers:

Layer 1:

newtype AppT m a = AppT { unAppT :: ReaderT YourStuff m a } deriving ............ The ReaderT Design Pattern, essentially. This is what everything gets boiled down to, and what everything eventually gets interpreted in. This type is the backbone of your app. For some components, you carry around some info/state (consider [MonadMetrics](https://hackage

etorreborre

#!/bin/bash

if [[ $# -ne 1 ]]; then
  echo "usage: $0 doc.md"
  echo
  echo 'Output will be printed to stdout, so you probably want to pipe to'
  echo 'pbcopy or to a file or something.'

  exit 1
fi