[v8-users] Re: [blink-dev] Intent to ship: Optimize await and AsyncFromSyncIterator

2018-09-28 Thread Sathya Gunasekaran 
On Fri, Sep 28, 2018 at 6:39 PM Sathya Gunasekaran 
wrote:

> LGTM
>
> On Fri, Sep 28, 2018 at 7:57 AM Maya Lekova  wrote:
>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Contact emailsmslek...@chromium.org
>> Explainerhttps://docs.google.com/document/d/1kL08cz4lR6gO5b2FATNK3QAfS8t-6K6kdk88U-n8tug/edit?usp=sharing
>> SpecThe
>> ECMAScript specification change reached consensus. Pull request:
>> https://github.com/tc39/ecma262/pull/1250
>> The tag review process is not
>> needed, TC39 consensus was reached instead.SummaryThe goal of this change
>> is to reduce the native “await” functionality to only take 1 tick on the
>> microtask queue instead of 3.Is this feature supported on all six Blink
>> platforms (Windows, Mac, Linux, Chrome OS, Android, and Android
>> WebView)?Yes.RisksInteroperability and CompatibilityEdge: ShippedFirefox:
>> No signalsSafari: No signalsWeb developers: Shouldn’t affect web
>> developers, as most of them transpile away async/await and Babel already
>> ships with the new behaviour.*
>>
>
Note: There's a web compat risk as this changes the observable order in
which promises created by async functions are resolved. Chrome plans to
ship this with a kill switch in case we hear about breakages in the wild.

We've decided not to add a use counter for this as it will lead to
unacceptable performance regressions.


>
>>
>> *ActivationThe new behaviour won’t affect the way async/await is being
>> used.Is this feature fully tested by web-platform-tests
>> ?Test262
>> tests are being implemented. We have related tests in the V8 repository in
>> test/inspector/debugger.Entry on the feature dashboard
>> Fits under
>> https://www.chromestatus.com/feature/5643236399906816
>> , as this is simply
>> an errata to the spec.*
>> ---
>> Best regards,
>> Maya
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFszerUqYez-STtMj1kEkjP1M%2BGm%2Bd07E7RNcY3%3DXn9rwZ57yQ%40mail.gmail.com
>> 
>> .
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Re: [blink-dev] Intent to ship: Optimize await and AsyncFromSyncIterator

2018-09-28 Thread Sathya Gunasekaran 
LGTM

On Fri, Sep 28, 2018 at 7:57 AM Maya Lekova  wrote:

>
>
>
>
>
>
>
>
>
>
> *Contact emailsmslek...@chromium.org
> Explainerhttps://docs.google.com/document/d/1kL08cz4lR6gO5b2FATNK3QAfS8t-6K6kdk88U-n8tug/edit?usp=sharing
> SpecThe
> ECMAScript specification change reached consensus. Pull request:
> https://github.com/tc39/ecma262/pull/1250
> The tag review process is not
> needed, TC39 consensus was reached instead.SummaryThe goal of this change
> is to reduce the native “await” functionality to only take 1 tick on the
> microtask queue instead of 3.Is this feature supported on all six Blink
> platforms (Windows, Mac, Linux, Chrome OS, Android, and Android
> WebView)?Yes.RisksInteroperability and CompatibilityEdge: ShippedFirefox:
> No signalsSafari: No signalsWeb developers: Shouldn’t affect web
> developers, as most of them transpile away async/await and Babel already
> ships with the new behaviour.ActivationThe new behaviour won’t affect the
> way async/await is being used.Is this feature fully tested by
> web-platform-tests
> ?Test262
> tests are being implemented. We have related tests in the V8 repository in
> test/inspector/debugger.Entry on the feature dashboard
> Fits under
> https://www.chromestatus.com/feature/5643236399906816
> , as this is simply
> an errata to the spec.*
> ---
> Best regards,
> Maya
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFszerUqYez-STtMj1kEkjP1M%2BGm%2Bd07E7RNcY3%3DXn9rwZ57yQ%40mail.gmail.com
> 
> .
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Fwd: Intent to ship: Optimize await and AsyncFromSyncIterator

2018-09-28 Thread Benedikt Meurer 
LGTM!

On Fri, Sep 28, 2018 at 4:06 PM Adam Klein  wrote:

> LGTM2
>
> On Fri, Sep 28, 2018 at 9:39 AM 'Mathias Bynens' via v8-users <
> v8-users@googlegroups.com> wrote:
>
>> LGTM
>>
>> On Fri, Sep 28, 2018 at 9:26 AM Maya Lekova 
>> wrote:
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *Contact emailsmslek...@chromium.org
>>> Explainerhttps://docs.google.com/document/d/1kL08cz4lR6gO5b2FATNK3QAfS8t-6K6kdk88U-n8tug/edit?usp=sharing
>>> SpecThe
>>> ECMAScript specification change reached consensus. Pull request:
>>> https://github.com/tc39/ecma262/pull/1250
>>> The tag review process is not
>>> needed, TC39 consensus was reached instead.SummaryThe goal of this change
>>> is to reduce the native “await” functionality to only take 1 tick on the
>>> microtask queue instead of 3.Is this feature supported on all six Blink
>>> platforms (Windows, Mac, Linux, Chrome OS, Android, and Android
>>> WebView)?Yes.RisksInteroperability and CompatibilityEdge: ShippedFirefox:
>>> No signalsSafari: No signalsWeb developers: Shouldn’t affect web
>>> developers, as most of them transpile away async/await and Babel already
>>> ships with the new behaviour.ActivationThe new behaviour won’t affect the
>>> way async/await is being used.Is this feature fully tested by
>>> web-platform-tests
>>> ?Test262
>>> tests are being implemented. We have related tests in the V8 repository in
>>> test/inspector/debugger.Entry on the feature dashboard
>>> Fits under
>>> https://www.chromestatus.com/feature/5643236399906816
>>> , as this is simply
>>> an errata to the spec.*
>>> ---
>>> Best regards,
>>> Maya
>>>
>>>
>>> --
>>> --
>>> v8-users mailing list
>>> v8-users@googlegroups.com
>>> http://groups.google.com/group/v8-users
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "v8-users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to v8-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "v8-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Benedikt Meurer

Software Engineer

bmeu...@google.com

Google Germany GmbH

Erika-Mann-Straße 33

80636 München

Geschäftsführer: Paul Manicle, Halimah DeLaine Prado

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

Diese E-Mail ist vertraulich. Falls sie diese fälschlicherweise erhalten
haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter,
löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen,
dass die E-Mail an die falsche Person gesendet wurde.



This e-mail is confidential. If you received this communication by mistake,
please don't forward it to anyone else, please erase all copies and
attachments, and please let me know that it has gone to the wrong person.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Fwd: Intent to ship: Optimize await and AsyncFromSyncIterator

2018-09-28 Thread Adam Klein 
LGTM2

On Fri, Sep 28, 2018 at 9:39 AM 'Mathias Bynens' via v8-users <
v8-users@googlegroups.com> wrote:

> LGTM
>
> On Fri, Sep 28, 2018 at 9:26 AM Maya Lekova  wrote:
>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Contact emailsmslek...@chromium.org
>> Explainerhttps://docs.google.com/document/d/1kL08cz4lR6gO5b2FATNK3QAfS8t-6K6kdk88U-n8tug/edit?usp=sharing
>> SpecThe
>> ECMAScript specification change reached consensus. Pull request:
>> https://github.com/tc39/ecma262/pull/1250
>> The tag review process is not
>> needed, TC39 consensus was reached instead.SummaryThe goal of this change
>> is to reduce the native “await” functionality to only take 1 tick on the
>> microtask queue instead of 3.Is this feature supported on all six Blink
>> platforms (Windows, Mac, Linux, Chrome OS, Android, and Android
>> WebView)?Yes.RisksInteroperability and CompatibilityEdge: ShippedFirefox:
>> No signalsSafari: No signalsWeb developers: Shouldn’t affect web
>> developers, as most of them transpile away async/await and Babel already
>> ships with the new behaviour.ActivationThe new behaviour won’t affect the
>> way async/await is being used.Is this feature fully tested by
>> web-platform-tests
>> ?Test262
>> tests are being implemented. We have related tests in the V8 repository in
>> test/inspector/debugger.Entry on the feature dashboard
>> Fits under
>> https://www.chromestatus.com/feature/5643236399906816
>> , as this is simply
>> an errata to the spec.*
>> ---
>> Best regards,
>> Maya
>>
>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "v8-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Fwd: Intent to ship: Optimize await and AsyncFromSyncIterator

2018-09-28 Thread 'Mathias Bynens' via v8-users 
LGTM

On Fri, Sep 28, 2018 at 9:26 AM Maya Lekova  wrote:

>
>
>
>
>
>
>
>
>
>
> *Contact emailsmslek...@chromium.org
> Explainerhttps://docs.google.com/document/d/1kL08cz4lR6gO5b2FATNK3QAfS8t-6K6kdk88U-n8tug/edit?usp=sharing
> SpecThe
> ECMAScript specification change reached consensus. Pull request:
> https://github.com/tc39/ecma262/pull/1250
> The tag review process is not
> needed, TC39 consensus was reached instead.SummaryThe goal of this change
> is to reduce the native “await” functionality to only take 1 tick on the
> microtask queue instead of 3.Is this feature supported on all six Blink
> platforms (Windows, Mac, Linux, Chrome OS, Android, and Android
> WebView)?Yes.RisksInteroperability and CompatibilityEdge: ShippedFirefox:
> No signalsSafari: No signalsWeb developers: Shouldn’t affect web
> developers, as most of them transpile away async/await and Babel already
> ships with the new behaviour.ActivationThe new behaviour won’t affect the
> way async/await is being used.Is this feature fully tested by
> web-platform-tests
> ?Test262
> tests are being implemented. We have related tests in the V8 repository in
> test/inspector/debugger.Entry on the feature dashboard
> Fits under
> https://www.chromestatus.com/feature/5643236399906816
> , as this is simply
> an errata to the spec.*
> ---
> Best regards,
> Maya
>
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Fwd: Intent to ship: Optimize await and AsyncFromSyncIterator

2018-09-28 Thread Maya Lekova 
*Contact emailsmslek...@chromium.org
Explainerhttps://docs.google.com/document/d/1kL08cz4lR6gO5b2FATNK3QAfS8t-6K6kdk88U-n8tug/edit?usp=sharing
SpecThe
ECMAScript specification change reached consensus. Pull request:
https://github.com/tc39/ecma262/pull/1250
The tag review process is not
needed, TC39 consensus was reached instead.SummaryThe goal of this change
is to reduce the native “await” functionality to only take 1 tick on the
microtask queue instead of 3.Is this feature supported on all six Blink
platforms (Windows, Mac, Linux, Chrome OS, Android, and Android
WebView)?Yes.RisksInteroperability and CompatibilityEdge: ShippedFirefox:
No signalsSafari: No signalsWeb developers: Shouldn’t affect web
developers, as most of them transpile away async/await and Babel already
ships with the new behaviour.ActivationThe new behaviour won’t affect the
way async/await is being used.Is this feature fully tested by
web-platform-tests
?Test262
tests are being implemented. We have related tests in the V8 repository in
test/inspector/debugger.Entry on the feature dashboard
Fits under
https://www.chromestatus.com/feature/5643236399906816
, as this is simply
an errata to the spec.*
---
Best regards,
Maya

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Arraybuffer

2018-09-28 Thread dan Med 
I appreciate your help, but still i can't seem to just understand the stack
calls and if i do that then i like to understand what thing should i do in
the code to get v8 execute those lines, well if my prievous question is out
of scope for v8-users how can i understand how they work ?
There is no doc

Il giorno ven 28 set 2018 alle ore 14:35 Caitlin Potter 
ha scritto:

> That question is probably out of scope for v8-users. The good news is,
> cs.chromium.org is very good at finding when things are called, how
> they’re used, etc.
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Arraybuffer

2018-09-28 Thread Caitlin Potter 
That question is probably out of scope for v8-users. The good news is, 
cs.chromium.org is very good at finding when things are called, how they’re 
used, etc.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Arraybuffer

2018-09-28 Thread dan Med 
as far as i know for me to get the method FileReaderLoader::OnReceivedData
called which will call the ArraybufferBuilder::Append this stack call has
to happen :
BlobReaderClientInterceptorForTesting::OnCalculatedSize --> call
--> OnCalculatedSize --> call --> OnDataPipeReadable --> call
--> OnReceivedData --> ArraybufferBuilder::Append.
now beforereading the entire code cause i need it for a thing, can someone
help me to understand when BlobReaderClientInterceptorForTesting i know it
is from the mojo IPC but nothing more. Like i don't know if the thread will
call this because there will be a file to read or what.

Il giorno ven 28 set 2018 alle ore 09:50 dan Med 
ha scritto:

> Yes, i was looking at something like this ^^
>
> Il giorno ven 28 set 2018 alle ore 07:06 Caitlin Potter 
> ha scritto:
>
>> You can find places where ArrayBufferBuilder::Append is called, by
>> looking for the ArrayBufferBuilder symbol on cs.chromium.org.
>>
>> For example, here’s one use of it:
>> https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/fileapi/file_reader_loader.cc?type=cs&g=0&l=260
>>
>> I don’t have an answer for your other question regarding the memory
>> layout (were you asking if the builder is a variably sized object, or if it
>> just holds a pointer to the variably sized byte array, or something else?)
>> — but hopefully you’ve had that cleared up already.
>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "v8-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Help

2018-09-28 Thread dan Med 
I'm sorry for my behaviour, probably it is because i think i went in most
of the directory but they didn't seem to get me to my answer.

Il giorno ven 28 set 2018 alle ore 04:03 Zac Hansen  ha
scritto:

> I'm not sure if you have social interaction problems, but you need to
> understand that your behavior in this mailing list is not appropriate.
> People have tried to help you with your questions, but you refuse to listen
> to what they have to say and seem to feel that you are owed support to your
> satisfaction by people you are not paying to help you.
>
> You need to have a bit of respect for the time and attention of other
> people and put in some actual effort yourself into solving your own
> problems instead of constantly sending emails to this list.
>
> Please look at other people asking for help and how they interact and
> you'll see that your behavior is SIGNIFICANTLY out of line with community
> expectations.
>
> On Thursday, September 27, 2018 at 2:05:16 PM UTC-7, dan Med wrote:
>>
>> yes under the WTF directory
>>
>> Il giorno gio 27 set 2018 alle ore 22:55 J Decker  ha
>> scritto:
>>
>>>
>>>
>>> On Thu, Sep 27, 2018 at 10:50 AM dan Med  wrote:
>>>
 When v8 calls the arraybufferappend method ?

>>> ARRAYBUFFERAPPEND IS NOT DEFINED IN V8 IT IS NEVER CALLED.
>>>
>>>

 Il giorno mar 4 set 2018 alle ore 12:12 Graham Reeves <
 gra...@grahamreeves.com> ha scritto:

> memcpy is this
> memcpy( writable_destination, const_source, length_in_bytes )
>
> if you're unsure what it's doing, expand the arguments so the code is
> more readable (shame on whoever wrote this :)
> memcpy(static_cast(buffer_->Data()) + bytes_used_,
> data,bytes_to_save);
> ...
> auto* Destination = static_cast(buffer_->Data()); // start of
> buffer
> Destination += bytes_used_; // offset from the start, same as
> Destination = &Destination[bytes_used_];
> memcpy(Destination, data, bytes_to_save );
>
> So to answer your question;
>
> > with this memcpy is it copying from data which is a const char
> pointer n bytes_to_save into the array buffer_
> No, it's copying the number of bytes *bytes_to_save* FROM *data*
> (from the start)
>
> >  into a specific offset from the array
> yes, into a specific offset from the start of the array *Buffer->Data*
>
> This isn't a v8 specific question, so you may get a better response
> for general C/++ questions on http://www.stackoverflow.com :)
>
>
> On Monday, 3 September 2018 19:55:35 UTC+1, dan Med wrote:
>>
>> Can someone help me out ?
>>
>> Il giorno dom 2 set 2018 alle ore 11:26  ha
>> scritto:
>>
>>>  memcpy(static_cast(buffer_->Data()) + bytes_used_,
>>> data,bytes_to_save);
>>>
>>> with this memcpy is it copying from data which is a const char
>>> pointer n bytes_to_save into the array buffer_ or into a specific offset
>>> from the array ?
>>>
>>> --
>>> --
>>> v8-users mailing list
>>> v8-u...@googlegroups.com
>>> http://groups.google.com/group/v8-users
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "v8-users" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to v8-users+u...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> v8-users mailing list
> v8-u...@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to the Google
> Groups "v8-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to v8-users+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
 --
 v8-users mailing list
 v8-u...@googlegroups.com
 http://groups.google.com/group/v8-users
 ---
 You received this message because you are subscribed to the Google
 Groups "v8-users" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to v8-users+u...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>>> --
>>> v8-users mailing list
>>> v8-u...@googlegroups.com
>>> http://groups.google.com/group/v8-users
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "v8-users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to v8-users+u...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-users" group.
> To unsubscribe from this group and stop receiving email

Re: [v8-users] Arraybuffer

2018-09-28 Thread dan Med 
Yes, i was looking at something like this ^^

Il giorno ven 28 set 2018 alle ore 07:06 Caitlin Potter 
ha scritto:

> You can find places where ArrayBufferBuilder::Append is called, by looking
> for the ArrayBufferBuilder symbol on cs.chromium.org.
>
> For example, here’s one use of it:
> https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/fileapi/file_reader_loader.cc?type=cs&g=0&l=260
>
> I don’t have an answer for your other question regarding the memory layout
> (were you asking if the builder is a variably sized object, or if it just
> holds a pointer to the variably sized byte array, or something else?) — but
> hopefully you’ve had that cleared up already.
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.