Skip to content

Conversation

@CobaltCause
Copy link

From "string literal" to basically still "string literal", but now you can use macros to generate the string literal. Did I mention string literals? Anyway, this is particularly useful in combination with the env!() macro and the environment variables cargo sets at build time.

See #28 for initial discussion. Also, I've done a force-push to add a few comments since then. And just to make things easier to follow/reference, I'll restate here that these changes currently require downstream crates to use a nightly toolchain due to rust-lang/rust#51911.

From "string literal" to basically still "string literal", but now you
can use macros to generate the string literal. Did I mention string
literals? Anyway, this is particularly useful in combination with the
`env!()` macro and the environment variables `cargo` sets at build time.
@poljar
Copy link
Owner

poljar commented Dec 2, 2020

Thanks, we'll wait for the nightly requirement to be lifted but it's nice to keep it here, also I don't really expect this PR to bitrot.

@jplatte
Copy link

jplatte commented Oct 6, 2021

While this implementation is probably fine, note that the unsafe usage can be removed once concat_bytes! is available.

@CobaltCause
Copy link
Author

I'm just going to close this since I honestly don't have any desire to fix this anymore. I think it should be possible to do this on stable rust now though if anyone else wants to pick it back up.

@CobaltCause CobaltCause closed this Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants