-
eseidel authored
This CL also makes it more clear in gin when type coercion fails what argument (0-indexed) failed to convert and what js type was seen in the process. I started down the path of logging the c++ destination type as well, but found I couldn't with our current RTTI-less build. This was already reviewed in: https://codereview.chromium.org/798163002/ before I realized that gin was maintained in chromium. TBR=abarth@chromium.org BUG= Review URL: https://codereview.chromium.org/805993002 Cr-Commit-Position: refs/heads/master@{#308435}
2584930f