Maybe this will help: all record types already exist when the type checker
starts. Even though there are no terms of that type, you could write x = {
bar = "foo" } and that value will be assigned the type { bar : String },
notice the equals in the value and the colon in the type.
So, type
It's not 100% clear to me what you want to do, but if you ping me on
#elm-dev on slack then I can probably help. Better to discuss it there
On Sat, Jan 7, 2017 at 12:18 PM, Peter Damoc wrote:
> I'm trying to explore how one could implement web-components in Elm natively
> using
On Friday, January 6, 2017 at 10:31:47 PM UTC, Birowsky wrote:
>
> It's not such a bummer since i can simply compose the reusable dom within
> Elm and I haven't had issues with shady dom, I'm just afraid what other
> Elm/Polymer inconsistencies are there..
>
Quite a few no doubt.
--
You
I'm trying to explore how one could implement web-components in Elm
natively using a minimal amount of Native code.
The approach I tried is to use some code from
https://github.com/WebReflection/dom-class
https://www.webreflection.co.uk/blog/2015/09/17/simplified-web-components-via-dom-class
and
I think this is a bug in elm-format
- https://github.com/avh4/elm-format/issues/162
On Friday, 6 January 2017 22:14:12 UTC, Rupert Smith wrote:
>
> On Friday, January 6, 2017 at 6:29:43 PM UTC, Mark Hamburg wrote:
>>
>> What is the intended usage of -- comments in Elm? I'm used to using them
>>