move main! macro to its own crate

[vitiral]

I mainly want this so I can steal it in and use it in stdcli!

vitiral/stdcli#2

[killercup]

Sure, I'm okay with that. It's just that there is at least one huge problem we need to solve:

What should we call this new crate?

(Some other, minor things: Do you want to have the cli parsing and logging stuff as well? If not, it might be easier to just copy the file actually.)

[killercup]

Some random ideas:

• mainly
• frankfurt (a city on the river Main – 2018 is the year crates are named after cities after all)

[vitiral]

Looking at the file more you might be right -- this macro is really the "tie together" point of your exported API. I think copy/paste might be the way to go.

I think if we could extract the "run" function ONLY that would be good. Such a macro would be generally useful for people's "basic template", at least until the new main semantics hit, to allow ppl to use ? in their main.

On that note, some possible names for a crate that is a shim to use ? and give good error messages could be:

• runaway
• mainline (like, mainlining a drug, in this case rust)

[killercup]

Hm, not sure if a crate like this pulls its own weight. I means, ?-in-main works in nightly already, incl. nice errors.

[vitiral]

ya, just waiting for nightly is probably good enough for now -- considering it is definitely something on the "hotpath" since it improves docs so much.

Closing this, although I really like the crate name mainline

[vitiral]

Also, I'm probably just going to inherit this crate as a dependency directly instead, as said in #19