Implementing native returns for constructor functions about boa

[jasonwilliams]

@vitkarpov sure!

[jasonwilliams]

@vitkarpov no problem, im still learning myself, mainly start on something then ask questions as needed

[jasonwilliams]

I've been thinking about this for some time, so sorry for the long write up.

@someguynamedmatt Number() doesn't work or exist at the moment, there is no Number object on the global scope at the that's where this ticket comes in: jasonwilliams#34
The number and String pattern in the description was just hypothetical and what we should be aiming for.

Our global function objects (String, Boolean, Array) need refactoring. If you look at the specification these are all function objects, which can create exotic objects or native data types, these function objects have [[Call]] and [[Construct]] internal methods. (this is easier to implement now now Objects have been refactored).

Let's take String as an example. String is exposed to the global scope as a function (make_string) with the methods on its prototype. This is ok for constucting objects but leaves us no room for calling String() normally.

Right now when we construct a new string, we actually just call it like a normal function. This means that in exec.rs Construct and Call are currently doing the same thing (except Construct passes this as its first argument)

Once function objects have been created exprDef::Construct will need to be more clever to return the [[Construct]] func, and ExprDef::Call will need to be more clever to return the [[Cal]] func

https://github.com/jasonwilliams/boa/blob/master/src/lib/js/string.rs#L556-L558 can go, ive not been a big fan of passing global in just to do that. Instead there should be a ::new() method which can be pulled into exec.rs

Refactoring
Functions (String(), Boolean(), Array()) should all be function objects to match https://tc39.es/ecma262/#function-object this can re-use https://github.com/jasonwilliams/boa/blob/master/src/lib/js/object.rs#L22-L31

Function Objects
https://tc39.es/ecma262/#function-object
A function object is just a regular object with the [[Call]] and [[Construct]] internal methods set

[vitkarpov]

Hey @jasonwilliams, it's nice that you have so clean descriptions of issues 👍 Do you consider to take a PR on this?

[jasonwilliams]

@vitkarpov ECMA spec defines 2 methods for calling and constructing an object, maybe this helps:
https://tc39.github.io/ecma262/#table-6

[jasonwilliams]

@vitkarpov how you getting on?

[vitkarpov]

@jasonwilliams now so good, actually I have a pretty basic understanding of Rust, so not being able to articulate in a particular language makes this kind of hard 😞

I'd be happy to follow your PRs and ask questions if you don't mind, I'm sure it's going to be better with time.

I'm sorry I didn't tell about it in advance if you're counting on me.

[someguynamedmatt]

@jasonwilliams For clarity: in the description are we suggesting that Number() works as intended, whereas String() doesn't? Or are they both not functioning to the spec?

[jasonwilliams]

A huge amount of the above work is now done. Constructor functions are now function objects which have a [[Construct]] and a [[Call]] method.
The Construct gets used here: https://github.com/jasonwilliams/boa/blob/master/src/lib/exec.rs#L281

Call currently doesn't use the [[Call]] internal slot.
https://github.com/jasonwilliams/boa/blob/master/src/lib/exec.rs#L111

@someguynamedmatt

This ticket may need to be broken out to others:
String: jasonwilliams#100