TylorS

Language Specification Wishes

The desire to create a new language has come from my own experiences in programming in a framework I’ve built, Motorcycle.js and the language TypeScript. Motorcycle is very similar to the more popular project Cycle.js. In my current place of employment we are building a rather large and complex application and we have felt the language barriers of ECMAScript and TypeScript much more than we have the programming patterns we have come to use.

This is, currently, a very informal and non-exhaustive list of things I wish a single programming language would have. This language would likely to be very opinionated, and geared towards functional and reactive web applications. In many ways, but not all, I’d like to see a language designed around the programming patterns of Cycle and Motorcycle.

I hope to develop this language in the future, unless someone else beats me to it! Following this is a

RadValentin

NOTE: This guide is ONLY for devs who don't want to edit their yarn.lock file by hand. If you don't care about that please carry on.

---

So you've pulled the latest master

git checkout master
git pull

briancavalier

// @flow
import { curry2, curry3 } from '@most/prelude'

export type Except<E, A> = Exception<E, A> | Result<E, A>

export const result = <E, A> (a: A): Except<E, A> =>
  new Result(a)

export const throwError = <E, A> (e: E): Except<E, A> =>
  new Exception(e)

briancavalier

// Pair helpers

// Map the first element of a pair
const first = <A, B, C> (f: A => B, [a, c]: [A, C]): [B, C] =>
  [f(a), c]

// Map the second element of a pair
const second = <A, B, C> (f: B => C, [a, b]: [A, B]): [A, C] =>
  [a, f(b)]