This is based on nixpkgs commit 862277ac9d34273cd953f42061e23d488d6b7e8b.
The resulting image is less than 25 MiB compressed.
The actual crosslink closure got shrunk from ~180 MiB to ~60 MiB just by using beam_minimal rather than beam as the base set in beams.nix!
It's come to my attention that some people have been spamming issue trackers with a link to this gist. While it's a good idea to inform people of the situation in principle, please do not do this. By all means spread the word in the communities that you are a part of, after verifying that they are not aware yet, but unsolicited spam is not helpful. It will just frustrate people.
A number of things have happened since the last update.
| -- Based on: http://augustss.blogspot.com/2007/10/simpler-easier-in-recent-paper-simply.html | |
| import Data.List (delete, union) | |
| {- HLINT ignore "Eta reduce" -} | |
| -- File mnemonics: | |
| -- env = typing environment | |
| -- vid = variable identifier in Bind or Var | |
| -- br = binder variant (Lambda or Pi) | |
| -- xyzTyp = type of xyz | |
| -- body = body of Lambda or Pi abstraction |
| (originally written in 2009 and posted to livejournal! https://jdimpson.livejournal.com/6812.html | |
| The last article teaches how to use socat by comparing it first to cat then to netcat. It skimped on socat's UDP-related features, because netcat only implements a subset of them. This article picks up where the last one left off, with respect to UDP. After this article will be one more that discusses advanced socat features. | |
| It turns out there are a lot of subleties when dealing with UDP, even before multicast is mixed in. We'll abandon the comparisons to netcat, as we've exceeded what netcat can do. But first a quick reminder of one way socat does UDP. | |
| socat as a UDP server on port 11111. | |
| socat STDIO UDP-LISTEN:11111 |
| {-# LANGUAGE GeneralisedNewtypeDeriving #-} | |
| module Data where | |
| type UserName = String | |
| data DataResult = DataResult String | |
| deriving (Eq, Show) | |
| class Monad m => Cache m where |
I believe the article was originally written by fede.tft.
It appears they have copied source code to github and updated it for C++11: https://github.com/fedetft/serial-port
The serial port protocol is one of the most long lived protocols currently in use. According to wikipedia, it has been standadized in 1969. First, a note: here we're talking about the RS232 serial protocol. This note is necessary because there are many other serial protocols, like SPI, I2C, CAN, and even USB and SATA.
Some time ago, when the Internet connections were done using a 56k modem, the serial port was the most common way of connecting a modem to a computer. Now that we have ADSL modems, the serial ports have disappeared from newer computers, but the protocol is still widely used.
In fact, most microcontrollers, even the newer ones have one or more peripherals capable of communicating using this protocol, and from the PC side, all operating system
| {-# LANGUAGE AllowAmbiguousTypes #-} | |
| {-# LANGUAGE ConstraintKinds #-} | |
| {-# LANGUAGE DataKinds #-} | |
| {-# LANGUAGE FlexibleContexts #-} | |
| {-# LANGUAGE FlexibleInstances #-} | |
| {-# LANGUAGE GADTs #-} | |
| {-# LANGUAGE GeneralizedNewtypeDeriving #-} | |
| {-# LANGUAGE InstanceSigs #-} | |
| {-# LANGUAGE KindSignatures #-} | |
| {-# LANGUAGE PolyKinds #-} |
Most people are familiar with these three tools:
The first one is more popular among developers because it is style-agnostic. The other two enforce rules of [Crockford Style][4] and [Google Code Style][5] respectively.
| {-# LANGUAGE | |
| DeriveFunctor | |
| , DeriveFoldable | |
| , DeriveTraversable | |
| , StandaloneDeriving | |
| , ViewPatterns | |
| , PatternSynonyms | |
| #-} | |
| -- AST independent |
| Shader | |
| layout (location = 0) in vec3 inPos; | |
| layout (location = 1) in vec3 inColor; | |
| layout (location = 2) in vec3 inPosB; | |
| layout (location = 3) in vec3 inColorB; | |
| ... | |
| Application |
