Name change proposal

[zedeus]

toast clashes with an ffmpeg dependency for GSM compression, so machines with an improperly setup path would cause nimterop to fail with a strange error message complaining about invalid arguments.

Maybe c2ast would be a fitting name? If nimterop plans to support more languages than C/C++ that would be inaccurate though. astgen or genast perhaps? ast2nim?

[genotrance]

Most of these might exist already - I think we might be better off going with nimterop itself since it is a quite unique name.

Open to feedback though.

[timotheecour]

anything starting with nim would be fine, eg toast => nimteropast (makes it clear it's related to nimterop)

[genotrance]

Really speaking, it is taking in an AST and generating Nim so it isn't to ast anymore.

Here's some other options:

• ast2nim
  -asterop
• nimtercli
• astercli

I can't call it nimterop since it will clash with the folder.

[timotheecour]

not smthg ud type everyday so maybe nimteropcli

[genotrance]

Once toast is a relative path from cimport, this won't be needed anymore. We can keep the name toast.

[genotrance]

Toast is now a relative path for cimport so that won't fail. If user wants to use on command line and it clashes, he can now give full path. I don't think we need to rename anymore. Please close if you agree.

[zedeus]

Fine with me.

[timotheecour]

on the other hand it's probably not too hard to fix assuming we can rename the generated binary, see #70 (comment) for an approach; tracking inhttps://github.com/nimterop/wrappers/issues/18 for a related issue