niconomaa

Results 10 issues of niconomaa

type: feature
P2: required
effort2: medium (days)
type: performance
comp: active expressions

The current implementation needs some refactoring, including: - changing of variable names - using `Reflect` instead of explicit target access - potentially finding an alternative to globally storing flags in...

P4: nice to have
effort1: easy (hours)
type: refactoring
comp: active expressions

type: feature
P2: required
effort3: hard (weeks)
comp: active expressions

`Array.from(aSet)` and other functions error with ``` Method Set.prototype.values called on incompatible receiver ``` This error is thrown in the `get` trap of the proxy handler and should be caught.

type: feature
P3: important
effort3: hard (weeks)
comp: active expressions

In some caases, as for example in Lively's AST Explorer, the source code transformation plugin that makes objects into Proxies was applied twice. While this is not to be expected,...

type: feature
P3: important
effort1: easy (hours)
comp: active expressions

In addition to Object expressions, we want to wrap `Call-` `Object-` and `New-`, `Function-`, `Class-` and potentially other expressions.

type: feature
P3: important
effort2: medium (days)
comp: active expressions

The proxy based implementation for active expression has been shown to be working for detecting changes in simple object property accesses and simple functions. Now, we need to test for...

Errors are returned inconsistently depending on the language used in the kernel cell. Consistent and useful error messages are desired.

Syntax highlighting is an important aspect of user experience. We want to introduce syntax highlighting in the notebook frontend for supported languages.

moonshot

Our basic approach to inform to kernel which language a notebook cell is using will be to use [magic commands](https://ipython.readthedocs.io/en/stable/interactive/magics.html). If time permits we want to be able to detect...

moonshot