<div dir="ltr">+1</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 27, 2015 at 3:27 PM, Loïc Hoguin <span dir="ltr"><<a href="mailto:essen@ninenines.eu" target="_blank">essen@ninenines.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 02/27/2015 03:17 PM, José Valim wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
1. {badmap, Term} - raised when a map was expected but got something<br>
else (this would replace the first error and it is an improvement over<br>
the error records used to raise)<br>
<br>
2. {badkey, Key, Map} - raised when we expected a Map to have Key but it<br>
does not. Useful for the := syntax and it could also be used if we ever<br>
add an access operation to maps<br>
<br>
If we segregate the errors as proposed, we will have plenty of<br>
opportunity to improve the reports in shell and in error loggers.<br>
<br>
Thoughts?<br>
</blockquote>
<br></span>
Sounds good.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Loïc Hoguin<br>
<a href="http://ninenines.eu" target="_blank">http://ninenines.eu</a><br>
______________________________<u></u>_________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/<u></u>listinfo/erlang-questions</a><br>
</font></span></blockquote></div><br></div>