rupertlssmith

module StateModel
    exposing
        ( boolToMaybe
        , (>&&>)
        , (>||>)
        , defaultTransition
        , mapWhenCompose
        )

import Maybe exposing (andThen)

rupertlssmith

module GameState
    exposing
        ( Game(..)
        , GameDefinition
        , PlayState
        , loading
        , updateGameDefinition
        , updatePlayState
        , updateScore
        , toReady

rupertlssmith

module Channels exposing (..)

import Html exposing (Html)
import Time exposing (Time, every, second)


-- Example


type alias Model =

rupertlssmith

module ProgramCombinator exposing (..)

import Html exposing (Html)
import Time exposing (Time, every, second)


-- Example


type alias Model =

rupertlssmith

module Traits exposing (..)


type GameState
    = State


{-| FireTrait defines how the game state is updated for any kind of shooting
event.
's' is the state implementation parameter,

rupertlssmith

module Tree
    exposing
        ( Tree
        , Zipper
        , Path
          -- Tree operations
        , singleton
        , zipper
        , map
          -- Zipper operations

rupertlssmith

module BasicSyntax exposing (..)

fact : Int -> Int
fact n =
    if n == 0 then
        1
    else
        n * fact (n - 1)
        
map : (a -> b) -> List a -> List b

rupertlssmith

-- This way gives you a custom type, which can be used to branch on in code with case of.

type Pet
    = Cat
    | Dog
    | Snake
    | Spider


petEnum =

rupertlssmith

port module Ports.LocalStoragePort exposing (clear, getItem, listKeys, response, setItem)

import LocalStorage exposing (ClearPort, GetItemPort, ListKeysPort, ResponsePort, SetItemPort)


port getItem : GetItemPort msg


port setItem : SetItemPort msg

rupertlssmith

Eco - An Alternate Elm Package Server

Eco is an alternative package management system for Elm. The name can stand for "Elm Compiler Offline".

The idea is to have a more configurable package management system for Elm, that allows for sharing private packages.

The main use case for this is intended to be within organizations, where a software developer or team can publish a private package that applications, or other private packages, in that organization can consume. This will support transitive dependency resolution in the same way that public Elm packages do.

The main repository and source of truth will be the existing package.elm-lang.org site.