A few cleanup/refactoring commits.

[frewsxcv]

No description provided.

[wycats]

@frewsxcv for the cases where we're making c-strings, does it make sense to use our cstr! macro that we use in other places?

[frewsxcv]

The cstr! macro only works when we're converting a string literal to a CStr, which is not the case for these lines. If you wanted to avoid doing this CString allocation here, you'd need to make the arguments to these functions/methods a &CStr instead of a &str, like this. Thoughts?

[wycats]

@frewsxcv I think that's acceptable. We don't intend the APIs you're changing to be ergonomic public APIs, but rather implementation details of the macro.

[frewsxcv]

Opened a PR: #88

Will rebase this once that lands

[frewsxcv]

rebased

[wagenet]

Thanks!