issa marie tseng

Right now to make janus-inspect work, we drop a reference to the parent data structure onto the generated Varying when we create a captive Varying (eg `list.length` or `map.get('key')`). But...

extend SomeClass.build() fails in ES6

1

``` TypeError: Cannot call a class constructor without |new| ``` where SomeClass is some ES6-generated Model.build classdef, for example. this happens because ES6 constructors cannot be called without keyword `new`,...

Alternative mutator system which uses requestAnimationFrame to reduce drawchurn

3

The primary complexity in implementing this is that rendering would no longer be synchronous. This is actually probably a great thing, because node.js does not like it if you spend...

When do we declare a flag? When do we check that flag before performing an operation? When might we use instanceof? Need clearer rules.

Once Models have immutable properties, one can consider detecting such cases and avoiding the reaction handlers to save on memory and processing.

So, m1 = new Map({ x: 42 }); m2 = m1.shadow(); m2.unset('x'); m2.enumeration(); should be empty. But right now it has x as null.

Including the simultaneous application of multiple changed args in a >1-arity Varying map. This still doesn't fix the overcomputation problem in the case where a `.react()` fires off a secondary...

And subsequently, implement flatMap.

Initially, just reject further changes. Often, application code (or thought processes thereof) can be vastly simplified with immutability assumptions, even with Janus's automatic handling. This mechanism gives peace of mind...