I believe this nicely addresses my concerns from the first proposal. Inner
refactoring into functions is 100% possible, and there are no strange
reassignment behaviors introduced that don't extend to the rest of the
language. As for the questions outlined in the guide:
1) To Paren or not Paren: Parens optional is best IMHO.
2) Naming for let: I like let.
3) Naming for reduce: I don't _love_ reduce but I think it's the best. It
is also no worse than Enum.reduce. Both are basically "for | Enum"
(indicating we are dealing with a collection) "reduce" ok into a single
managed value.
4) Limitations to patterns right now: I'm 100% with limiting let to `let
var` or `let {tuple, of, vars}` for now. This can always be relaxed later.
All in all, very happy with where this proposal has landed, and tantalized
by the future possibilities!
On Monday, December 20, 2021 at 1:18:24 PM UTC-5 Dunya Kirkali wrote:
>
> This guide is super useful. Maybe we should use it to update the docs?
> On Monday, December 20, 2021 at 7:12:09 PM UTC+1 José Valim wrote:
>
>> Hi everyone,
>>
>> This is the second proposal for-let. You can find it in a gist:
>> https://gist.github.com/josevalim/fe6b0bcc728539a5adf9b2821bd4a0f5
>>
>> Please use the mailing list for comments and further discussion. Thanks
>> for all the feedback so far!
>>
>
--
You received this message because you are subscribed to the Google Groups
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elixir-lang-core/0c3c0ab5-b9a7-412b-aed8-43ea6efc05a8n%40googlegroups.com.
