Corbin Simpson

Specifically, turn [these worst cases for elementary transcendental functions](http://perso.ens-lyon.fr/jean-michel.muller/TMDworstcases.pdf) into test cases.

Structured tracing and logging

1

We should have some sort of structured logging. At a minimum, `traceln()` should support structured arguments.

Port benchmarking to pure Monte with Timer

2

This probably depends on fixing `Timer` to not suck.

It's About Time

10

Timing effects generated by the `tokenBucket` and `loopingCall` modules are terrible. When I try to reason about their behavior, I'm rapidly blocked by a lack of clear semantics for `Timer`...

Next-generation file resource API

1

This is now the discussion issue for API to replace `makeFileResource`. Summary: * Path segments should be guarded by `def Path := Any[Str, Bytes]`; under the hood, the runtime should...

Next MAST Version: No More Meta

4

We are removing the `meta.context()` and `meta.getState()` nodes from MAST, as we intend to add them to canonical expansion instead. Since we are only removing nodes, we technically do not...

$ monte new

2

Subcommand for creating a new skeleton package and populating mt.json. This subcommand could take switches for package name. Or perhaps it should directly take a package name, as in: $...

`astBuilder` is not a great name

1

I would like us to consider the direction of putting the AST builder builder in the safe scope, perhaps under the `astBuilder` name, or perhaps as `makeAstBuilder`, analogous to `makeLazySlot`....

I haven't been able to get a stack overflow for some reason, but: def x := [1, x]; x x

Currently, we have no spread syntax, leading often to: ``` M.call(f, "run", args, [].asMap()) ``` We should investigate whether there are better ways to express this.