Paul Harper
Paul Harper
Using the platform template as my reference, it looks like `.tmx` files in `scripts/levels` are referring to assets as if they were in `scripts` rather than `assets`. For example, the...
Normally, you also get the index of the current item and the object being iterated over. Instead, the arguments should only contain values (at least for reduce) so that we...
Array destructuring: ``` (def array [1 2 3 4 5]) (def [a b c ...d] array) (= a 1) (= b 2) (= c 3) (= d [4 5]) ```...
Example: ``` (print [:a :b :c]) ;; ["a", "b", "c"] (print `(def a :b)) ;; [["symbol", "def"], ["symbol", "a"], "b"] ``` It would be nice if these were prettier
Currently, all macros reside in a single object. We should be able to namespace them, to avoid name collisions.
``` (def five {:valueOf #(do 5) :toString #(do "five")}) (->str five) ;; should yield "five", yields "5" ``` this is because we are using the `str` function for string conversion,...
Are there plans to develop a method to easily generate a javascript for...in loop like: ``` javascript var obj = {a: 'a', b: 'b'} for (var key in obj) {...
And when this is fixed, it would also be nice if `break` statements aren't required. They're silly. I would like something like: ``` switch foo { case :bar: aha() case...
Async function calls don't respect functions accessed from an object with the bracket syntax. The specific error is: `Error: Unexpected token: operator (!)`
An example error: `TypeError: Object function __defineSetter__() { [native code] } has no method 'tail'` This doesn't occur when simply writing this.__define(G/S)etter.