Ah, yup that looks fine. I had thought about adding some functions like this to
Pcg but never got around to it. One of these days...
--
You received this message because you are subscribed to the Google Groups "Elm
Discuss" group.
To unsubscribe from this group and stop receiving emails from
Sure, I just copied the function definition to my module that uses
Random.Pcg instead of Random.
There was no need to change the implementation, it just uses
Random.Pcg.constant instead of Random.Extra.constant, I believe.
import Random.Pcg as Random exposing (Generator)
{-| Turn a list of
> I have created my own Random.Pcg `together` and it compiles.
Would you mind clarifying what you mean by this?
--
You received this message because you are subscribed to the Google Groups "Elm
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
The namespaces get 'merged' - ie. if you do:
module A exposing (a, b, c)
---
module B exposing (d, e, f)
---
module C exposing (..)
import A
import B as A
then nothing's wrong - you can do A.a through to A.f without a problem.
Problems happen when collision happens, ie.
module B exposing (c)
Why are duplicate imports allowed in the first place?
On Friday, August 19, 2016 at 2:20:50 AM UTC-5, Martin Janiczek wrote:
>
> Hello,
>
> I've been stumped by a compiler error which I can't figure out. I think
> it's a compiler bug. (I'd like to maybe help fix that and contribute a PR -
>
