Hi all,
First of all let me say that I'm really liking the language and the
ecosystem and the more I use it the more it's growing on me.
It's been hard letting go of some of the preconceptions I had from previous
programming languages, but reading through evan's threads and applying the
design decisions that Elm encourages now it's starting to pay off as I see
more how everything fits together nicely.
I have a couple of non-related questions and I don't know if this is the
right place to ask, but here we go :)
1) I come from a clojure background and I find updating records in Elm has
pretty cumbersome syntax.
Why does the update syntax accept just a new value instead of accepting a
function that updates (or creates) the new value?
Example
{model | val = 42}
as opposed to:
{model | val = increase}
or
{model | val = (always 42) }
I observed there are more cases when you need to update the existing value
rather than setting a new one explicitly and I was wondering why Elm
encourages the first syntax
2) I love the fact that Elm has fuzzy test support out of the box.
But why isn't the ability to create fuzzy records/data available outside
that package? What I usually do is to stub out the UI given a certain model
type. Being able to call fuzzy generators in my Main namespace to populate
the model makes it easier iterate on an initial design and can still be
very useful to run the application in 'mock mode'. Any chance we can see
the generators extracted in their own library?
Thanks everyone in advance!
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
