iomonad

/**
    * @note SourceShape Graph, runnable as Source.
    */
  override def graph: Graph[SourceShape[FileMessage], NotUsed] = GraphDSL.create() { implicit b =>

    import GraphDSL.Implicits._

    val TCK = b.add(Source.tick[SmartjogClient]
      (0.second, interval, client))

qoomon

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
 -m"<optional body>" \

iomonad

syntax = "proto3";

option java_multiple_files = true;
option java_package = "fr.canal.rocket.configuration.grpc";
option java_outer_classname = "IngestRulesProto";

package ingestrule;

enum TransportType {
    ASPERA = 0;

Icelandjack

import Data.Functor.Yoneda
import Data.Char
import Data.Kind

infixr 5
  ·

type  List :: (Type -> Type) -> Constraint
class List f where

iomonad

import akka.actor.ActorSystem
import akka.stream._
import akka.stream.scaladsl._

import scala.io.StdIn
import scala.util.Random

object SimplePartitionSample extends App {

  implicit val system = ActorSystem()

robey

;
; the "monitor ROM" of an apple 1 fit in one page (256 bytes).
;
; this is my attempt to take the disassembled code, give names to the
; variables and routines, and try to document how it worked.
;
;
; an apple 1 had 8KB of RAM (more, if you hacked on the motherboard), and a
; peripheral chip that drove the keyboard and video. the video was run by a
; side processor that could treat the display as an append-only terminal that

davideicardi

/*
https://scalafiddle.io/sf/sniohcZ/3
(old version: https://scalafiddle.io/sf/sniohcZ/1)

Use PassThroughFlow when you have a message that should be used in a 
flow that trasform it but you want to maintain the original message for
another following flow.
For example if you consume messages from Kafka (CommittableMessage).
You process the message (transform, save it inside a database, ...) and then you need again the original message 
to commit the offset.

gvolpe

Dependency Injection in Functional Programming

There exist several DI frameworks / libraries in the Scala ecosystem. But the more functional code you write the more you'll realize there's no need to use any of them.

A few of the most claimed benefits are the following:

• Dependency Injection.
• Life cycle management.
• Dependency graph rewriting.

iomonad

;                                   D O O M
;%%%%%  %%%%%  %%%%  %%%%%% %%  %%   _---_   %%%  %%%  %%%%  %%%%%%  %%%% %%  %%
;%%  %% %%    %%  %%   %%   %%  %% ."     ". %%%%%%%% %%  %%   %%   %%    %%  %%
;%%  ## ####  ######   ##   ###%%% | () () | %% %# ## ######   ##   ##    ###%%%
;## ,## ##    ##  ##   ##   ## `##  \  A  /  ## #= ## ##  ##   ##   ##    ## `##
;####=  =###= =#  #=   =#   =#  ##  |"+++"|  ## =- #= =#  #=   =#    ###= =#  ##
;##=                            =#   "---"   #=                               =#
;                                 WAD RANKING

    .name "dwarf"

iomonad

#include <stdio.h>

int
main(int argc, char *argv[])
{
	int i = 0;

	i ^= i&~-~i|~i&-~i;
	printf("%d\n", i);
	return (0);