Add ArrayBuffer/DataView/Symbol/#toString. Improve Errors

[MaxGraey]

No description provided.

[dcodeIO]

Afaik this is never null in JS

[MaxGraey]

Yes, but it could be undefined according to this

Or not?

[MaxGraey]

Actually Error.prototype.stack is not standard but all browsers support it

[dcodeIO]

My initial though was that if it's guaranteed to be a string, even if empty, one can simply print it without having to check explicitly, which is about what you'd do in JS because it's effectively always there.

[MaxGraey]

Ok, I'll revert this

[dcodeIO]

Looks like this should be the default case of the switch above

[MaxGraey]

Yeah, make sense

[dcodeIO]

Thanks! :)

[chicoxyzzy]

What about Symbol.toStringTag?

[dcodeIO]

That should be there.

[chicoxyzzy]

Yes, but I mean

class ArrayBuffer {
  ...
  get [Symbol.toStringTag]() { // should be added
    return 'ArrayBuffer';
  }
  ...
}

Object.prototype.toString.call(new ArrayBuffer()); // to make this work

[dcodeIO]

While the symbols are there, these aren't really supported yet. [Symbol.something] syntax for properties isn't there yet, for example. The most prominent reason for having them defined already is that there are plans to implement iterators eventually, but it is unlikely that something like Function#call, as in your snippet, will be supported because it would imply that an untyped argument is provided, which isn't really AOT compatible, in turn rendering some of the built-in symbols like toStringTag obsolete.

[chicoxyzzy]

makes sense, thanks for the explanation