> That said perhaps the first version of the EEP can change binary() to
> #{binary() => binary()} as this part is unlikely to change, and require
> that the map contains at least one element where the key is <<"en">>. That
> way tools can experiment with translations in a backward compatible manner.
>

Agreed. Those concerns seem to mostly apply to the projects consuming the
chunks. Figuring out the language in the shell isn't the same as in the
browser. Changing to a map now will allow this experimentation to happen
(maybe even motivate it).

Thanks Loïc!
_______________________________________________
eeps mailing list
[email protected]
http://erlang.org/mailman/listinfo/eeps

Reply via email to