-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement dynamic string interpolation #10318
Comments
I agree that this needs a library interface to be more useful. The original intent with the new format strings was to allow extensions for things like i18n and such, and even programs such as this could in theory be possible. I don't think that there's any feasible usage outside of a macro due to the way it's structured. You're right in that this would likely require that all the arguments implement the same trait instead of having a mixture of possible traits. I would recommend taking a look at the expansion of the Sadly I'm not sure that this would be entirely useful until we get syntax extension import/export working because I do really think that this belongs in a library as opposed to the compiler (which I would love to move fmt::{print,format,println} to the prelude). |
FWIW, something like |
Additional use case (unless there's a way to currently do this I haven't noticed): struct Record {
name: ~str,
message: ~str
// etc...
}
struct Logger {
name: ~str,
stream: Writer,
fmt: ~str
}
impl Logger {
fn log(&mut self, message: ~str) {
self.stream.write_line(self.format(Record{name:self.name, message: message}));
}
fn format(&mut self, record: Record) {
std::format::dynamic_format(self.fmt, record) // <-- use case
}
fn setFormat(&mut self, format: ~str) {
self.fmt = format;
}
}
// else where
logger.setFormat(~"{name}.{level}: {message}"); |
I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized. This issue has been moved to the RFCs repo: rust-lang/rfcs#642 |
Fix false positives for `extra_unused_type_parameters` Don't lint external macros. Also, if the function body is empty, any type parameters with bounds on them are not linted. Note that only the body needs be empty - this rule still applies if the function takes any arguments. fixes rust-lang#10318 fixes rust-lang#10319 changelog: none <!-- changelog_checked -->
In a perfect world, a minimal quine in Rust would look like this:
Sadly, this is impossible. Why? Because
println!
requires that the first argument not just be static; it must be a string literal.There are other, non-contrived use cases for dynamic string interpolation; acrichto mentions internationalization as one example.
So what would be involved in implementing dynamic string interpolation?
acrichto mentions (https://botbot.me/mozilla/rust/msg/7556963/) that the current machinery used to parse strings for
format!
provides an interface that could be reused (std::fmt
). But that's only part of the solution.The first issue is that we can't guarantee type safety for dynamic interpolation (can we???), so the syntax for dynamic format strings might need to be rethought. For now we should probably assume that all arguments to dynamic string interpolation will implement
ToStr
and just ignore any format string options that aren't for positional or named arguments.The second issue is that we can't just simply have anything like a simple
.format()
method on strings, like Python has, since we don't have variadic functions. We'd need to either do something like pass an array of trait objects:...or use method chaining and generics:
(all code examples are just quick sketches, might be overlooking details (and don't worry about naming))
Any thoughts?
The text was updated successfully, but these errors were encountered: