There is no internal ramification that I am aware of that would prevent us
from doing so AFAICT. So +1 from my side. Just my two cents.

Best regards,
Michael

On Tue, May 24, 2016 at 7:20 PM, Adam Klein <[email protected]> wrote:

> Thanks for the pointers. I think I was too sloppy (ha ha!) in my initial
> message: it's the C++ builtins in particular that I noticed were
> always-sloppy. Is that something we can just change without any
> ramifications? It wasn't clear to me if that was for some internal reason.
>
> On Tue, May 24, 2016 at 7:52 AM, Michael Starzinger <
> [email protected]> wrote:
>
>> See issue: https://bugs.chromium.org/p/v8/issues/detail?id=3752
>>
>> Best regards,
>> Michael
>>
>> On Tue, May 24, 2016 at 4:12 AM, Benedikt Meurer <[email protected]>
>> wrote:
>>
>>> Hey Adam,
>>>
>>> I think that this is not even consistent; as you point out, some
>>> builtins are strict (the js ones), while others are sloppy. I think this is
>>> for historical reasons, because initially everything was sloppy, and then
>>> we migrated some of the js files to strict mode. But so far no one payed
>>> attention to the non-js builtin function maps. Feel free to fix that.
>>>
>>> -- Benedikt
>>>
>>> Adam Klein <[email protected]> schrieb am Di., 24. Mai 2016, 00:33:
>>>
>>>> While looking at a test262 bug (
>>>> https://bugs.chromium.org/p/v8/issues/detail?id=4925) I ran into an
>>>> old problem: it seems that our builtin functions are always sloppy mode,
>>>> which means that they inappropriately have 'caller' and 'arguments' own
>>>> properties (
>>>> https://bugs.chromium.org/p/chromium/issues/detail?id=516666).
>>>>
>>>> Does anyone have some background on this? How tricky would it be to
>>>> make our builtins "strict"? It seems unfortunate that code written in C++
>>>> reflects as sloppy (Array.prototype.push, for example) while code written
>>>> in JS is strict (Map.prototype.get, e.g.).
>>>>
>>>> - Adam
>>>>
>>>> --
>>>> --
>>>> v8-dev mailing list
>>>> [email protected]
>>>> http://groups.google.com/group/v8-dev
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "v8-dev" 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.
>>>>
>>> --
>>> --
>>> v8-dev mailing list
>>> [email protected]
>>> http://groups.google.com/group/v8-dev
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "v8-dev" 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.
>>>
>>
>> --
>> --
>> v8-dev mailing list
>> [email protected]
>> http://groups.google.com/group/v8-dev
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "v8-dev" 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.
>>
>
> --
> --
> v8-dev mailing list
> [email protected]
> http://groups.google.com/group/v8-dev
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-dev" 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.
>

-- 
-- 
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- 
You received this message because you are subscribed to the Google Groups 
"v8-dev" 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.

Reply via email to