I really want to just write something like:
newmodel = { model | field.deeper.deeperer = "new value" }
People have pointed me towards something Evan wrote about discouraging
this, but I still don't understand why it would be a bad idea.
It would reduce quite a bit of boilerplate.
At the moment it just encourages me to keep everything flat, so rather than
having a nested record I will do something like make lots of fields so I
can write things like:
newmodel = {model | field_deeper_deeperer = "new value" }
Terrible, I know.
On Friday, 3 March 2017 06:12:39 UTC, Richard Feldman wrote:
>
> There have been various discussions of potential ways to improve Elm's
> record update syntax. Evan commented that "(examples > design work) at this
> point" - any potential designs for syntax improvements would need to be run
> through a gauntlet of examples to see how well they'd work, so the first
> step in the process is to gather those examples.
>
> So let's collect a ton of different real-world examples! That will help
> guide the design process.
>
> If you've run into a record update that you felt was painful and could be
> improved in some way, please post it here! (Also, *please keep this
> thread for posting of examples* *only* - it'll be easier to link back
> here during design discussions if we can reference a clean thread of
> examples, as opposed to a mismash of examples interleaved with suggestions.)
>
--
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.
