Agreed, I'll remove them from the polyfill.
On Wed, Aug 21, 2013 at 10:34 PM, David Herman dher...@mozilla.com wrote:
On Aug 21, 2013, at 12:49 PM, Dmitry Lomov dslo...@chromium.org wrote:
I really hope that uint64 from value type spec and uint64 from typed
object spec are one and same
to be honest I thought those were Symbols rather than some type/brand
representation and as symbols I've shimmed them too.
Float32Array is a thing already, I honestly wouldn't mind Int32, Uint32,
Uint64, Float32, Float64 and other constructors too in the global scope
since I don't see any other
I lie it = I like it (and not a lie at all)
On Wed, Aug 21, 2013 at 10:55 AM, Andrea Giammarchi
andrea.giammar...@gmail.com wrote:
to be honest I thought those were Symbols rather than some type/brand
representation and as symbols I've shimmed them too.
Float32Array is a thing already, I
The intention has always been for them to be in a module. I'll make that
clearer on the wiki.
Dave
On Aug 21, 2013, at 10:42 AM, K. Gadd k...@luminance.org wrote:
moving back onto list
It might be worth doing. On the one hand, I don't really feel like these
names *should* collide with
If necessary, i.e. if people want to release it before modules, we can make it
available in a single top-level object, but I would not at all favor dumping
everything onto the global scope.
Dave
On Aug 21, 2013, at 12:07 PM, David Herman dher...@mozilla.com wrote:
The intention has always
is T as single top level object an option?
is any of these an option: typed, types, type, or TypedObject ?
if not, which one would be ?
On Wed, Aug 21, 2013 at 12:09 PM, David Herman dher...@mozilla.com wrote:
If necessary, i.e. if people want to release it before modules, we can
make it
On Wed, Aug 21, 2013 at 7:42 PM, K. Gadd k...@luminance.org wrote:
moving back onto list
It might be worth doing. On the one hand, I don't really feel like these
names *should* collide with anything, but it seems like the risk is kinda
high... and it's a little weird seeing them in global
On Aug 21, 2013, at 12:49 PM, Dmitry Lomov dslo...@chromium.org wrote:
I really hope that uint64 from value type spec and uint64 from typed object
spec are one and same thing (we now in typed objects spec allow using
uint8/uint16/.. co to be used as conversion functions).
Agreed, and my
8 matches
Mail list logo
