cedar-lang / cedar Goto Github PK

objects like lists, vectors, dicts, etc... should be immutable. ie: no set methods

This will result in much uglier code for said macro expander, but it is also a good testing ground for the language as it is being developed

This should be implemented as a pass before the bytecode emission

When a lambda is called, it does a memory allocation... It needs to not do this. Possibly wrap calls in a pass-by-value struct that has a closure pointer and a pointer to the lambda itself. This is cause a lambda object is currently massive and takes alot of time to allocate. Also, function calls should not allocate memory outside of stack resizes and closures...

Instead of running the main thread as a repl thread and whatnot, I think the main thread needs to convert itself into a scheduler thread after all it's command line parsing is done. This is what most languages do, and I dont really see why cedar needs to be different. This would mean converting the repl into a cedar program, but that's not really a problem.