It's more a question of the stability of the language specification. I don't doubt the code is solid enough for production sites; it's just that keeping up with Arc's evolution might be difficult. But as I pointed out, you might not need to do that. (I edited the original comment to be more clear.)
i don't arc is intended to have more than one implementation, or at least more than one popular implementation. if this is the case, nothing is unspecified. whatever the implementation does, that is the language.
the problem that other people have stated is that because arc's macros are unhygienic, allowing local variables to shadow macros causes some pretty serious problems.
thing that annoys me is there is nothing for arc that is anything close to what slime is for cl. i would settle for an inferior arc mode. my emacs skills are not good enough to take this into my own hands, i'm afraid.
Me neither, but I gave it a shot. I use it and it works, there may be bugs though. Maybe an Emacs guru will be kind enough to point out the errors I may have introduced while adapting cmuscheme.el.
it's a good start. the bugs i see immediately are it lets you erase the prompt and the prompt appears when results are printed too. i might see if there is a way to solve these problems.
the latest changes in anarki for the --no-rl option fix the problem with the repeated prompt. so now it's just that the prompt can be deleted, which is a really minor issue.
