Evan Hubinger

So, I looked into the package linked at the top, and it's actually pretty good. By 0.2.0, it means `sublime-coconut` 0.2.0, which actually maps to Coconut 1.1.0, not Coconut 0.2.0,...

@dylanjm Glad to hear you're liking Coconut! I don't think you'd be able to use Coconut inside of another file, though compiling just a chunk of a file is something...

@dylanjm Theoretically, you could do something like ```python from coconut.convenience import parse exec(parse(""" """)) ``` though that is definitely less than ideal. If all you want is LaTeX exporting, though,...

@ArneBachmann Yeah, this is a known issue. MyPy can't handle the redefinition of `__new__`, so it doesn't know that the argument has been made optional. I'll keep this open and...

TRE is now enabled even with `--no-tco`, so the first point on this is now moot. The second still stands, but that check unlikely to make much of a difference...

Another thing `@recursive` could do, though, would be assert that TRE actually was applied to any functions decorated with it.

It's time to abandon `_coconut`. We should move to normal built-in names and `py_` names for old built-ins. If `--strict` is passed, Coconut should issue a warning on use of...

If we ever do this, we'll have to find a way to rewrite the tests that rely on it, and find a new way to mock out `typing` in the...

This should allow support for both compile-time optimization like so ``` meta expensive_func_memo: return {arg: arg |> expensive_func for arg in common_args_to_expensive_func} ``` and embedded metaprogramming like so ``` meta...

Also added should be a simple in-line meta assignment like ``` meta concatenated_string = ( "line 1" "line 2" "line 3" ) ``` or from the above example ``` meta...