Boris REDNBLACK

Every Argument for Static Typing Applies to Typed Errors

Think of all the arguments you've heard as to why static typing is desirable — every single one of those arguments applies equally well to using types to represent error conditions.

An odd thing I’ve observed about the Scala community is how many of its members believe that a) a language with a sophisticated static type system is very valuable; and b) that using types for error handling is basically a waste of time. If static types are useful—and if you like Scala, presumably you think they are—then using them to represent error conditions is also useful.

Here's a little secret of functional programming: errors aren't some special thing that operate under a different set of rules to everything else. Yes, there are a set of common patterns we group under the loose heading "error handling", but fundamentally we're just dealing with more values. Values that can have types associated with them. There's absolutely no reason why the benefits of static ty

Fibers

Fibers are an abstraction over sequential computation, similar to threads but at a higher level. There are two ways to think about this model: by example, and abstractly from first principles. We'll start with the example.

(credit here is very much due to Fabio Labella, who's incredible Scala World talk describes these ideas far better than I can)

Callback Sequentialization

Consider the following three functions

Install nginx (Homebrew)

brew install nginx

Configuration file for nginx will be at /usr/local/etc/nginx/nginx.conf

Web apps can be stored at /usr/local/var/www

Commands

Start:

This gist will no longer be updated as the changelog will be on the official website.

Sublime Text/Merge Official Discord chat server: https://discord.gg/D43Pecu
Sublime Text/Merge 中文 Telegram 交流群組： https://t.me/sublime_tw

Converted via https://domchristie.github.io/turndown

About Sublime Text 4

Easy Scala Publication

The following describes how you can publish artifacts for any sbt project using the GitHub Package Registry and the sbt-github-packages plugin.

Step 1: Create a GitHub Token

In your GitHub account, go to Settings > Developer settings > Personal access tokens, then click on Generate new token (or click here). Fill in some sort of meaningful name (I chose Dev) and click on the write:packages checkbox:

	{
	"CFBundleDocumentTypes": [
	{
	"CFBundleTypeName": "Folder",
	"CFBundleTypeRole": "Viewer",
	"LSItemContentTypes": [
	"public.folder"
	]
	},
	{

	import tensorflow as tf #We need tensorflow 2.x
	import numpy as np

	#The hashlength in bits
	hashLength = 256

	def buildModel():
	#we can set the seed to simulate the fact that this network is known and doesn't change between runs
	#tf.random.set_seed(42)
	model = tf.keras.Sequential()

	#!/usr/bin/osascript -l JavaScript
	// ^^^^ COMMENT/REMOVE THIS SHEBANG IF RUNNING FROM SCRIPT EDITOR!!!!! ^^^^^^^^^^^
	// The SHEBANG is only needed if the file is executable and is run from a terminal with `./RsyncBackup.js`

	// 1. In MacOS Spotlight type 'Script Editor' and paste the code below
	// 2. Click the top-left dropdown which says 'AppleScript' and select 'JavaScript'
	// 3. Under menu File pick Export
	// 4. In the Export dialog select File Format = Application
	// 5. Save the app in /Applications

	#!/bin/bash

	input="$(pwd)/domains.txt"
	outputFile="$(pwd)/vpnc_server_script.sh"
	routerSSH="[email protected]"

	addOps=()
	delOps=()
	ipAddrRegular='[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}$'



	sealed trait Path

	case class Field(name: String, child: Option[Path]) extends Path {
	override def toString: String = child match {
	case None => name
	case Some(path) => s"$name.$path"
	}
	}