* Feature(Number): Tests for the Test Driven Development!
refs #34
* Feature: Skeleton code for Number
refs #34
* Feature: Most of Number() is complete
Includes:
- make_number()
- call_number()
- Number().toExponential()
- Number().toFixed()
- Number().toLocaleString() (ish)
- Number().toString()
- Number().valueOf()
- create_constructor()
- init()
Missing:
- Number().toPrecision()
refs #34
* Feature(Number): test compatability with const -> var
I don't have all the context on _why_ but all of the tests for `Number` started failing.
Upon investigation it was becuase `const` stopped acting the way I expected.
Switching my test cases from using `const` to using `var` variable declarations
made everything work again. I don't know enough about JS to know if this is a
bug or expected behavior. Based on changes to other tests, it is know
behavior.
Refs #34
* Changelog: Number() object.
Includes some clippy fixes.
Fixes#34
* Added create_constructor method
* Updated global to use json::create_constructor method
* unassigned var is undefined (#125)
* Unassigned variables are set to `undefined` not `null`
Fixes#113
* Rust tests for `var x` and `let x` default to undefined
* CHANGELOG for issue #113 fix + add tests/js/test.js to gitignore.
* fixing PR benchmarks (#132)
* fixing PR benchmarks
* Push after rebase
* Updated import order
* Formatting
* Unassigned variables are set to `undefined` not `null`
Fixes#113
* Rust tests for `var x` and `let x` default to undefined
* CHANGELOG for issue #113 fix + add tests/js/test.js to gitignore.