elm-rails 0.2.0 → 0.2.1

data/test/rails4.2/elm-stuff/packages/elm-lang/core/5.0.0/src/Platform.elm

@@ -1,145 +0,0 @@
-module Platform exposing
-  ( Program, program, programWithFlags
-  , Task, ProcessId
-  , Router, sendToApp, sendToSelf
-  )
-
-{-|
-
-# Programs
-@docs Program, program, programWithFlags
-
-# Platform Internals
-
-## Tasks and Processes
-@docs Task, ProcessId
-
-## Effect Manager Helpers
-
-An extremely tiny portion of library authors should ever write effect managers.
-Fundamentally, Elm needs maybe 10 of them total. I get that people are smart,
-curious, etc. but that is not a substitute for a legitimate reason to make an
-effect manager. Do you have an *organic need* this fills? Or are you just
-curious? Public discussions of your explorations should be framed accordingly.
-
-@docs Router, sendToApp, sendToSelf
--}
-
-import Basics exposing (Never)
-import Native.Platform
-import Native.Scheduler
-import Platform.Cmd exposing (Cmd)
-import Platform.Sub exposing (Sub)
-
-
-
--- PROGRAMS
-
-
-{-| A `Program` describes how to manage your Elm app.
-
-You can create [headless][] programs with the [`program`](#program) and
-[`programWithFlags`](#programWithFlags) functions. Similar functions exist in
-[`Html.App`][app] that let you specify a view.
-
-[headless]: https://en.wikipedia.org/wiki/Headless_software
-[app]: http://package.elm-lang.org/packages/elm-lang/html/latest/Html-App
-
-Honestly, it is totally normal if this seems crazy at first. The best way to
-understand is to work through [guide.elm-lang.org](http://guide.elm-lang.org/).
-It makes way more sense in context!
--}
-type Program flags model msg = Program
-
-
-{-| Create a [headless][] program. This is great if you want to use Elm as the
-“brain” for something else. You can still communicate with JS via
-ports and manage your model, you just do not have to specify a `view`.
-
-[headless]: https://en.wikipedia.org/wiki/Headless_software
-
-Initializing a headless program from JavaScript looks like this:
-
-```javascript
-var app = Elm.MyThing.worker();
-```
--}
-program
-  : { init : (model, Cmd msg)
-    , update : msg -> model -> (model, Cmd msg)
-    , subscriptions : model -> Sub msg
-    }
-  -> Program Never model msg
-program =
-  Native.Platform.program
-
-
-{-| Same as [`program`](#program), but you can provide flags. Initializing a
-headless program (with flags) from JavaScript looks like this:
-
-```javascript
-var app = Elm.MyThing.worker({ user: 'Tom', token: 1234 });
-```
-
-Whatever argument you provide to `worker` will get converted to an Elm value,
-allowing you to configure your Elm program however you want from JavaScript!
--}
-programWithFlags
-  : { init : flags -> (model, Cmd msg)
-    , update : msg -> model -> (model, Cmd msg)
-    , subscriptions : model -> Sub msg
-    }
-  -> Program flags model msg
-programWithFlags =
-  Native.Platform.programWithFlags
-
-
-
--- TASKS and PROCESSES
-
-{-| Head over to the documentation for the [`Task`](Task) module for more
-information on this. It is only defined here because it is a platform
-primitive.
--}
-type Task err ok = Task
-
-
-{-| Head over to the documentation for the [`Process`](Process) module for
-information on this. It is only defined here because it is a platform
-primitive.
--}
-type ProcessId = ProcessId
-
-
-
--- EFFECT MANAGER INTERNALS
-
-
-{-| An effect manager has access to a “router” that routes messages between
-the main app and your individual effect manager.
--}
-type Router appMsg selfMsg =
-  Router
-
-
-{-| Send the router a message for the main loop of your app. This message will
-be handled by the overall `update` function, just like events from `Html`.
--}
-sendToApp : Router msg a -> msg -> Task x ()
-sendToApp =
-  Native.Platform.sendToApp
-
-
-{-| Send the router a message for your effect manager. This message will
-be routed to the `onSelfMsg` function, where you can update the state of your
-effect manager as necessary.
-
-As an example, the effect manager for web sockets
--}
-sendToSelf : Router a msg -> msg -> Task x ()
-sendToSelf =
-  Native.Platform.sendToSelf
-
-
-hack =
-  Native.Scheduler.succeed

data/test/rails4.2/elm-stuff/packages/elm-lang/core/5.0.0/src/Platform/Cmd.elm

@@ -1,67 +0,0 @@
-module Platform.Cmd exposing
-  ( Cmd
-  , map
-  , batch
-  , none
-  , (!)
-  )
-
-{-|
-
-# Effects
-
-Elm has **managed effects**, meaning that things like HTTP requests or writing
-to disk are all treated as *data* in Elm. When this data is given to the Elm
-runtime system, it can do some “query optimization” before actually performing
-the effect. Perhaps unexpectedly, this managed effects idea is the heart of why
-Elm is so nice for testing, reuse, reproducibility, etc.
-
-There are two kinds of managed effects you will use in your programs: commands
-and subscriptions.
-
-@docs Cmd, map, batch, none, (!)
-
--}
-
-import Native.Platform
-
-
-{-| A command is a way of telling Elm, “Hey, I want you to do this thing!”
-So if you want to send an HTTP request, you would need to command Elm to do it.
-Or if you wanted to ask for geolocation, you would need to command Elm to go
-get it.
-
-Every `Cmd` specifies (1) which effects you need access to and (2) the type of
-messages that will come back into your application.
-
-**Note:** Do not worry if this seems confusing at first! As with every Elm user
-ever, commands will make more sense as you work through [the Elm Architecture
-Tutorial](http://guide.elm-lang.org/architecture/index.html) and see how they
-fit into a real application!
--}
-type Cmd msg = Cmd
-
-
-{-|-}
-map : (a -> msg) -> Cmd a -> Cmd msg
-map =
-  Native.Platform.map
-
-
-{-|-}
-batch : List (Cmd msg) -> Cmd msg
-batch =
-  Native.Platform.batch
-
-
-{-|-}
-none : Cmd msg
-none =
-  batch []
-
-
-{-|-}
-(!) : model -> List (Cmd msg) -> (model, Cmd msg)
-(!) model commands =
-  (model, batch commands)
-

data/test/rails4.2/elm-stuff/packages/elm-lang/core/5.0.0/src/Platform/Sub.elm

@@ -1,52 +0,0 @@
-module Platform.Sub exposing
-  ( Sub
-  , map
-  , batch
-  , none
-  )
-
-{-|
-
-@docs Sub, map, batch, none
--}
-
-import Native.Platform
-
-
-{-| A subscription is a way of telling Elm, “Hey, let me know if anything
-interesting happens over there!” So if you want to listen for messages on a web
-socket, you would tell Elm to create a subscription. If you want to get clock
-ticks, you would tell Elm to subscribe to that. The cool thing here is that
-this means *Elm* manages all the details of subscriptions instead of *you*.
-So if a web socket goes down, *you* do not need to manually reconnect with an
-exponential backoff strategy, *Elm* does this all for you behind the scenes!
-
-Every `Sub` specifies (1) which effects you need access to and (2) the type of
-messages that will come back into your application.
-
-**Note:** Do not worry if this seems confusing at first! As with every Elm user
-ever, subscriptions will make more sense as you work through [the Elm Architecture
-Tutorial](http://guide.elm-lang.org/architecture/index.html) and see how they fit
-into a real application!
--}
-type Sub msg = Sub
-
-
-{-|-}
-map : (a -> msg) -> Sub a -> Sub msg
-map =
-  Native.Platform.map
-
-
-{-|-}
-batch : List (Sub msg) -> Sub msg
-batch =
-  Native.Platform.batch
-
-
-{-|-}
-none : Sub msg
-none =
-  batch []
-
-

data/test/rails4.2/elm-stuff/packages/elm-lang/core/5.0.0/src/Process.elm

@@ -1,106 +0,0 @@
-module Process exposing
-  ( Id
-  , spawn
-  , sleep
-  , kill
-  )
-
-{-|
-
-# Processes
-@docs Id, spawn, sleep, kill
-
-## Future Plans
-
-Right now, this library is pretty sparse. For example, there is no public API
-for processes to communicate with each other. This is a really important
-ability, but it is also something that is extraordinarily easy to get wrong!
-
-I think the trend will be towards an Erlang style of concurrency, where every
-process has an “event queue” that anyone can send messages to. I currently
-think the API will be extended to be more like this:
-
-    type Id exit msg
-
-    spawn : Task exit a -> Task x (Id exit Never)
-
-    kill : Id exit msg -> Task x ()
-
-    send : Id exit msg -> msg -> Task x ()
-
-A process `Id` will have two type variables to make sure all communication is
-valid. The `exit` type describes the messages that are produced if the process
-fails because of user code. So if processes are linked and trapping errors,
-they will need to handle this. The `msg` type just describes what kind of
-messages this process can be sent by strangers.
-
-We shall see though! This is just a draft that does not cover nearly everything
-it needs to, so the long-term vision for concurrency in Elm will be rolling out
-slowly as I get more data and experience.
-
-I ask that people bullish on compiling to node.js keep this in mind. I think we
-can do better than the hopelessly bad concurrency model of node.js, and I hope
-the Elm community will be supportive of being more ambitious, even if it takes
-longer. That’s kind of what Elm is all about.
--}
-
-import Basics exposing (Never)
-import Native.Scheduler
-import Platform
-import Task exposing (Task)
-import Time exposing (Time)
-
-
-{-| A light-weight process that runs concurrently. You can use `spawn` to
-get a bunch of different tasks running in different processes. The Elm runtime
-will interleave their progress. So if a task is taking too long, we will pause
-it at an `andThen` and switch over to other stuff.
-
-**Note:** We make a distinction between *concurrency* which means interleaving
-different sequences and *parallelism* which means running different
-sequences at the exact same time. For example, a
-[time-sharing system](https://en.wikipedia.org/wiki/Time-sharing) is definitely
-concurrent, but not necessarily parallel. So even though JS runs within a
-single OS-level thread, Elm can still run things concurrently.
--}
-type alias Id =
-  Platform.ProcessId
-
-
-{-| Run a task in its own light-weight process. In the following example,
-`task1` and `task2` will be interleaved. If `task1` makes a long HTTP request
-or is just taking a long time, we can hop over to `task2` and do some work
-there.
-
-    spawn task1
-      |> Task.andThen (\_ -> spawn task2)
-
-**Note:** This creates a relatively restricted kind of `Process` because it
-cannot receive any messages. More flexibility for user-defined processes will
-come in a later release!
--}
-spawn : Task x a -> Task y Id
-spawn =
-  Native.Scheduler.spawn
-
-
-{-| Block progress on the current process for a given amount of time. The
-JavaScript equivalent of this is [`setTimeout`][setTimeout] which lets you
-delay work until later.
-
-[setTimeout]: https://developer.mozilla.org/en-US/docs/Web/API/WindowTimers/setTimeout
--}
-sleep : Time -> Task x ()
-sleep =
-  Native.Scheduler.sleep
-
-
-{-| Sometimes you `spawn` a process, but later decide it would be a waste to
-have it keep running and doing stuff. The `kill` function will force a process
-to bail on whatever task it is running. So if there is an HTTP request in
-flight, it will also abort the request.
--}
-kill : Id -> Task x ()
-kill =
-  Native.Scheduler.kill
-

data/test/rails4.2/elm-stuff/packages/elm-lang/core/5.0.0/src/Random.elm

@@ -1,532 +0,0 @@
-effect module Random where { command = MyCmd } exposing
-  ( Generator, Seed
-  , bool, int, float
-  , list, pair
-  , map, map2, map3, map4, map5
-  , andThen
-  , minInt, maxInt
-  , generate
-  , step, initialSeed
-  )
-
-{-| This library helps you generate pseudo-random values.
-
-This library is all about building [`generators`](#Generator) for whatever
-type of values you need. There are a bunch of primitive generators like
-[`bool`](#bool) and [`int`](#int) that you can build up into fancier
-generators with functions like [`list`](#list) and [`map`](#map).
-
-It may be helpful to [read about JSON decoders][json] because they work very
-similarly.
-
-[json]: https://evancz.gitbooks.io/an-introduction-to-elm/content/interop/json.html
-
-> *Note:* This is an implementation of the Portable Combined Generator of
-L'Ecuyer for 32-bit computers. It is almost a direct translation from the
-[System.Random](http://hackage.haskell.org/package/random-1.0.1.1/docs/System-Random.html)
-module. It has a period of roughly 2.30584e18.
-
-# Generators
-@docs Generator
-
-# Primitive Generators
-@docs bool, int, float
-
-# Data Structure Generators
-@docs pair, list
-
-# Custom Generators
-@docs map, map2, map3, map4, map5, andThen
-
-# Generate Values
-@docs generate
-
-# Generate Values Manually
-@docs step, Seed, initialSeed
-
-# Constants
-@docs maxInt, minInt
-
--}
-
-import Basics exposing (..)
-import List exposing ((::))
-import Platform
-import Platform.Cmd exposing (Cmd)
-import Task exposing (Task)
-import Time
-import Tuple
-
-
-
--- PRIMITIVE GENERATORS
-
-
-{-| Create a generator that produces boolean values. The following example
-simulates a coin flip that may land heads or tails.
-
-    type Flip = Heads | Tails
-
-    coinFlip : Generator Flip
-    coinFlip =
-        map (\b -> if b then Heads else Tails) bool
--}
-bool : Generator Bool
-bool =
-  map ((==) 1) (int 0 1)
-
-
-{-| Generate 32-bit integers in a given range.
-
-    int 0 10   -- an integer between zero and ten
-    int -5 5   -- an integer between -5 and 5
-
-    int minInt maxInt  -- an integer in the widest range feasible
-
-This function *can* produce values outside of the range [[`minInt`](#minInt),
-[`maxInt`](#maxInt)] but sufficient randomness is not guaranteed.
--}
-int : Int -> Int -> Generator Int
-int a b =
-  Generator <| \(Seed seed) ->
-    let
-      (lo,hi) =
-        if a < b then (a,b) else (b,a)
-
-      k = hi - lo + 1
-      -- 2^31 - 87
-      base = 2147483561
-      n = iLogBase base k
-
-      f n acc state =
-        case n of
-          0 -> (acc, state)
-          _ ->
-            let
-              (x, nextState) = seed.next state
-            in
-              f (n - 1) (x + acc * base) nextState
-
-      (v, nextState) =
-        f n 1 seed.state
-    in
-      ( lo + v % k
-      , Seed { seed | state = nextState }
-      )
-
-
-iLogBase : Int -> Int -> Int
-iLogBase b i =
-  if i < b then
-    1
-  else
-    1 + iLogBase b (i // b)
-
-
-{-| The maximum value for randomly generated 32-bit ints: 2147483647 -}
-maxInt : Int
-maxInt =
-  2147483647
-
-
-{-| The minimum value for randomly generated 32-bit ints: -2147483648 -}
-minInt : Int
-minInt =
-  -2147483648
-
-
-{-| Generate floats in a given range. The following example is a generator
-that produces decimals between 0 and 1.
-
-    probability : Generator Float
-    probability =
-        float 0 1
--}
-float : Float -> Float -> Generator Float
-float a b =
-  Generator <| \seed ->
-    let
-      (lo, hi) =
-        if a < b then (a,b) else (b,a)
-
-      (number, newSeed) =
-        step (int minInt maxInt) seed
-
-      negativeOneToOne =
-        toFloat number / toFloat (maxInt - minInt)
-
-      scaled =
-        (lo+hi)/2 + ((hi-lo) * negativeOneToOne)
-    in
-      (scaled, newSeed)
-
-
-
--- DATA STRUCTURES
-
-
-{-| Create a pair of random values. A common use of this might be to generate
-a point in a certain 2D space. Imagine we have a collage that is 400 pixels
-wide and 200 pixels tall.
-
-    randomPoint : Generator (Int,Int)
-    randomPoint =
-        pair (int -200 200) (int -100 100)
-
--}
-pair : Generator a -> Generator b -> Generator (a,b)
-pair genA genB =
-  map2 (,) genA genB
-
-
-{-| Create a list of random values.
-
-    floatList : Generator (List Float)
-    floatList =
-        list 10 (float 0 1)
-
-    intList : Generator (List Int)
-    intList =
-        list 5 (int 0 100)
-
-    intPairs : Generator (List (Int, Int))
-    intPairs =
-        list 10 <| pair (int 0 100) (int 0 100)
--}
-list : Int -> Generator a -> Generator (List a)
-list n (Generator generate) =
-  Generator <| \seed ->
-    listHelp [] n generate seed
-
-
-listHelp : List a -> Int -> (Seed -> (a,Seed)) -> Seed -> (List a, Seed)
-listHelp list n generate seed =
-  if n < 1 then
-    (List.reverse list, seed)
-
-  else
-    let
-      (value, newSeed) =
-        generate seed
-    in
-      listHelp (value :: list) (n-1) generate newSeed
-
-
-
--- CUSTOM GENERATORS
-
-
-{-| Transform the values produced by a generator. The following examples show
-how to generate booleans and letters based on a basic integer generator.
-
-    bool : Generator Bool
-    bool =
-      map ((==) 1) (int 0 1)
-
-    lowercaseLetter : Generator Char
-    lowercaseLetter =
-      map (\n -> Char.fromCode (n + 97)) (int 0 25)
-
-    uppercaseLetter : Generator Char
-    uppercaseLetter =
-      map (\n -> Char.fromCode (n + 65)) (int 0 25)
-
--}
-map : (a -> b) -> Generator a -> Generator b
-map func (Generator genA) =
-  Generator <| \seed0 ->
-    let
-      (a, seed1) = genA seed0
-    in
-      (func a, seed1)
-
-
-{-| Combine two generators.
-
-This function is used to define things like [`pair`](#pair) where you want to
-put two generators together.
-
-    pair : Generator a -> Generator b -> Generator (a,b)
-    pair genA genB =
-      map2 (,) genA genB
-
--}
-map2 : (a -> b -> c) -> Generator a -> Generator b -> Generator c
-map2 func (Generator genA) (Generator genB) =
-  Generator <| \seed0 ->
-    let
-      (a, seed1) = genA seed0
-      (b, seed2) = genB seed1
-    in
-      (func a b, seed2)
-
-
-{-| Combine three generators. This could be used to produce random colors.
-
-    import Color
-
-    rgb : Generator Color.Color
-    rgb =
-      map3 Color.rgb (int 0 255) (int 0 255) (int 0 255)
-
-    hsl : Generator Color.Color
-    hsl =
-      map3 Color.hsl (map degrees (int 0 360)) (float 0 1) (float 0 1)
--}
-map3 : (a -> b -> c -> d) -> Generator a -> Generator b -> Generator c -> Generator d
-map3 func (Generator genA) (Generator genB) (Generator genC) =
-  Generator <| \seed0 ->
-    let
-      (a, seed1) = genA seed0
-      (b, seed2) = genB seed1
-      (c, seed3) = genC seed2
-    in
-      (func a b c, seed3)
-
-
-{-| Combine four generators.
--}
-map4 : (a -> b -> c -> d -> e) -> Generator a -> Generator b -> Generator c -> Generator d -> Generator e
-map4 func (Generator genA) (Generator genB) (Generator genC) (Generator genD) =
-  Generator <| \seed0 ->
-    let
-      (a, seed1) = genA seed0
-      (b, seed2) = genB seed1
-      (c, seed3) = genC seed2
-      (d, seed4) = genD seed3
-    in
-      (func a b c d, seed4)
-
-
-{-| Combine five generators.
--}
-map5 : (a -> b -> c -> d -> e -> f) -> Generator a -> Generator b -> Generator c -> Generator d -> Generator e -> Generator f
-map5 func (Generator genA) (Generator genB) (Generator genC) (Generator genD) (Generator genE) =
-  Generator <| \seed0 ->
-    let
-      (a, seed1) = genA seed0
-      (b, seed2) = genB seed1
-      (c, seed3) = genC seed2
-      (d, seed4) = genD seed3
-      (e, seed5) = genE seed4
-    in
-      (func a b c d e, seed5)
-
-
-{-| Chain random operations, threading through the seed. In the following
-example, we will generate a random letter by putting together uppercase and
-lowercase letters.
-
-    letter : Generator Char
-    letter =
-      bool
-        |> andThen upperOrLower
-
-    upperOrLower : Bool -> Generator Char
-    upperOrLower b =
-      if b then uppercaseLetter else lowercaseLetter
-
-    -- bool : Generator Bool
-    -- uppercaseLetter : Generator Char
-    -- lowercaseLetter : Generator Char
--}
-andThen : (a -> Generator b) -> Generator a -> Generator b
-andThen callback (Generator generate) =
-  Generator <| \seed ->
-    let
-      (result, newSeed) =
-        generate seed
-
-      (Generator genB) =
-        callback result
-    in
-      genB newSeed
-
-
-
--- IMPLEMENTATION
-
-
-{-| A `Generator` is like a recipe for generating certain random values. So a
-`Generator Int` describes how to generate integers and a `Generator String`
-describes how to generate strings.
-
-To actually *run* a generator and produce the random values, you need to use
-functions like [`generate`](#generate) and [`initialSeed`](#initialSeed).
--}
-type Generator a =
-    Generator (Seed -> (a, Seed))
-
-
-type State = State Int Int
-
-
-{-| A `Seed` is the source of randomness in this whole system. Whenever
-you want to use a generator, you need to pair it with a seed.
--}
-type Seed =
-  Seed
-    { state : State
-    , next  : State -> (Int, State)
-    , split : State -> (State, State)
-    , range : State -> (Int,Int)
-    }
-
-
-{-| Generate a random value as specified by a given `Generator`.
-
-In the following example, we are trying to generate a number between 0 and 100
-with the `int 0 100` generator. Each time we call `step` we need to provide a
-seed. This will produce a random number and a *new* seed to use if we want to
-run other generators later.
-
-So here it is done right, where we get a new seed from each `step` call and
-thread that through.
-
-    seed0 = initialSeed 31415
-
-    -- step (int 0 100) seed0 ==> (42, seed1)
-    -- step (int 0 100) seed1 ==> (31, seed2)
-    -- step (int 0 100) seed2 ==> (99, seed3)
-
-Notice that we use different seeds on each line. This is important! If you use
-the same seed, you get the same results.
-
-    -- step (int 0 100) seed0 ==> (42, seed1)
-    -- step (int 0 100) seed0 ==> (42, seed1)
-    -- step (int 0 100) seed0 ==> (42, seed1)
--}
-step : Generator a -> Seed -> (a, Seed)
-step (Generator generator) seed =
-  generator seed
-
-
-{-| Create a &ldquo;seed&rdquo; of randomness which makes it possible to
-generate random values. If you use the same seed many times, it will result
-in the same thing every time! A good way to get an unexpected seed is to use
-the current time.
--}
-initialSeed : Int -> Seed
-initialSeed n =
-  Seed
-    { state = initState n
-    , next = next
-    , split = split
-    , range = range
-    }
-
-
-{-| Produce the initial generator state. Distinct arguments should be likely
-to produce distinct generator states.
--}
-initState : Int -> State
-initState seed =
-  let
-    s = max seed -seed
-    q  = s // (magicNum6-1)
-    s1 = s %  (magicNum6-1)
-    s2 = q %  (magicNum7-1)
-  in
-    State (s1+1) (s2+1)
-
-
-magicNum0 = 40014
-magicNum1 = 53668
-magicNum2 = 12211
-magicNum3 = 52774
-magicNum4 = 40692
-magicNum5 = 3791
-magicNum6 = 2147483563
-magicNum7 = 2147483399
-magicNum8 = 2147483562
-
-
-next : State -> (Int, State)
-next (State state1 state2) =
-  -- Div always rounds down and so random numbers are biased
-  -- ideally we would use division that rounds towards zero so
-  -- that in the negative case it rounds up and in the positive case
-  -- it rounds down. Thus half the time it rounds up and half the time it
-  -- rounds down
-  let
-    k1 = state1 // magicNum1
-    rawState1 = magicNum0 * (state1 - k1 * magicNum1) - k1 * magicNum2
-    newState1 = if rawState1 < 0 then rawState1 + magicNum6 else rawState1
-    k2 = state2 // magicNum3
-    rawState2 = magicNum4 * (state2 - k2 * magicNum3) - k2 * magicNum5
-    newState2 = if rawState2 < 0 then rawState2 + magicNum7 else rawState2
-    z = newState1 - newState2
-    newZ = if z < 1 then z + magicNum8 else z
-  in
-    (newZ, State newState1 newState2)
-
-
-split : State -> (State, State)
-split (State s1 s2 as std) =
-  let
-    new_s1 =
-      if s1 == magicNum6-1 then 1 else s1 + 1
-
-    new_s2 =
-      if s2 == 1 then magicNum7-1 else s2 - 1
-
-    (State t1 t2) =
-      Tuple.second (next std)
-  in
-    (State new_s1 t2, State t1 new_s2)
-
-
-range : State -> (Int,Int)
-range _ =
-    (0, magicNum8)
-
-
-
--- MANAGER
-
-
-{-| Create a command that will generate random values.
-
-Read more about how to use this in your programs in [The Elm Architecture
-tutorial][arch] which has a section specifically [about random values][rand].
-
-[arch]: https://evancz.gitbooks.io/an-introduction-to-elm/content/architecture/index.html
-[rand]: https://evancz.gitbooks.io/an-introduction-to-elm/content/architecture/effects/random.html
--}
-generate : (a -> msg) -> Generator a -> Cmd msg
-generate tagger generator =
-  command (Generate (map tagger generator))
-
-
-type MyCmd msg = Generate (Generator msg)
-
-
-cmdMap : (a -> b) -> MyCmd a -> MyCmd b
-cmdMap func (Generate generator) =
-  Generate (map func generator)
-
-
-init : Task Never Seed
-init =
-  Time.now
-    |> Task.andThen (\t -> Task.succeed (initialSeed (round t)))
-
-
-onEffects : Platform.Router msg Never -> List (MyCmd msg) -> Seed -> Task Never Seed
-onEffects router commands seed =
-  case commands of
-    [] ->
-      Task.succeed seed
-
-    Generate generator :: rest ->
-      let
-        (value, newSeed) =
-          step generator seed
-      in
-        Platform.sendToApp router value
-          |> Task.andThen (\_ -> onEffects router rest newSeed)
-
-
-onSelfMsg : Platform.Router msg Never -> Never -> Seed -> Task Never Seed
-onSelfMsg _ _ seed =
-  Task.succeed seed