So, my suspicion was correct, I am using DataView methods like this
(https://github.com/Ayms/abstract-tls/blob/master/lib/abstract-tls.js#l280-332
here and on other projects) for historical reasons, because I started
from node.js's buffers methods and then switched to ArrayBuffers with
I've been through the thread and I haven't read any use case that
*requires* Weak References. Only use cases where they make life easier to
various degrees. It's been agreed that in most cases, adding an explicit
.dispose() or equivalent protocol could work too.
Very few things added to ES6 is
On 28 March 2013 21:42, Mark S. Miller erig...@google.com wrote:
prohibitively depends on your tolerance. Modern machines can usually do
register-to-register byte order reversal rather speedily. Which big endian
machines do you have in mind?
For WebGL, which expects native endianness on its
On 28 March 2013 23:01, David Herman dher...@mozilla.com wrote:
On Mar 27, 2013, at 6:51 AM, Andreas Rossberg rossb...@google.com wrote:
There actually are (third-party) projects
with ports of V8 and/or Chromium to big endian architectures.
It would be helpful to have more information about
On Wed, Apr 3, 2013 at 2:13 AM, Marius Gundersen gunder...@gmail.comwrote:
I've been through the thread and I haven't read any use case that
*requires* Weak References. Only use cases where they make life easier to
various degrees. It's been agreed that in most cases, adding an explicit
I mean, a stack-allocated, immutable, simple, value type, for high-performance
uses. ___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
On 4/3/2013 8:54 AM, BelleveInvis wrote:
I mean, a stack-allocated, immutable, simple, value type, for
high-performance uses.
http://wiki.ecmascript.org/doku.php?id=strawman:tuples
___
es-discuss mailing list
es-discuss@mozilla.org
Le 03/04/2013 17:54, BelleveInvis a écrit :
I mean, a stack-allocated, immutable, simple, value type, for
high-performance uses.
I think binary data [1] is very close to what you're looking for.
stack-allocated is complicated to ask. It really depends on what the
JS interpreters decides to do
Le 03/04/2013 11:13, Marius Gundersen a écrit :
A core part of the problem here is that the distinction between an
'important' reference - one that must keep an object alive - and an
'incidental' reference, that only need exist as long as it target does...
This is a concept which cannot be
On Wed, Apr 3, 2013 at 11:20 AM, David Bruant bruan...@gmail.com wrote:
Le 03/04/2013 11:13, Marius Gundersen a écrit :
A core part of the problem here is that the distinction between an
'important' reference - one that must keep an object alive - and an
'incidental' reference, that only
Le 03/04/2013 21:18, Mark S. Miller a écrit :
Do languages which added WeakRefs have a form of revokable
reference too? What difference would it make?
E has both. In practice, my sense is that their use cases are
disjoint, and that both are needed.
Do you have examples of use? May
On Wed, Apr 3, 2013 at 1:10 PM, David Bruant bruan...@gmail.com wrote:
Le 03/04/2013 21:18, Mark S. Miller a écrit :
Do languages which added WeakRefs have a form of revokable reference
too? What difference would it make?
E has both. In practice, my sense is that their use cases are
I've added a wiki page with the function name proposal that was agreed
upon [1]. It expands in more detail the original proposal and provides
examples for most ways a function can be named.
One issue is statics were introduced after the proposal was written.
Right now I simply have them take
On Fri, Mar 29, 2013 at 5:04 PM, Allen Wirfs-Brock
al...@wirfs-brock.com wrote:
On Mar 29, 2013, at 3:02 PM, Peter Michaux wrote:
15.16.4.6
Why will callbackfn be called with the first two parameters being the
same? That does not seem like the most practical or intuitive behavior
for a
14 matches
Mail list logo
