Hello, I am the author of the strfmt library.

I would like to push the stdlib to implement fmt::Formatter as a trait instead of a struct so that libraries like ours can use (and build off of) a common API, as well as format any object which implements the fmt::Display trait.

This issue is to bring this to your attention and try to work together on it.

vitiral/strfmt#11

Hi,
I have a (for simplicity) &[(String, String)], where first String corresponds to Args::name and the second String corresponds to Args::Value (of type Value::Str). How do I convert this to the Args struct? I can't get around the pub prev: Option<&'a Args<'a>> reference hell in the Args struct.

That is, I need to implement

fn to_args(args: &[(String, String)]) -> Args {
  unimplemented!()
}

Any idea? Thank you.

Edit: It does not need to actually be a function. I'll use the resulting args to format the message immediately, so if there's a way to produce the Args inline, I'd be happy with that as well.

I'm not happy at all with how arguments work right now. Something clearly better is needed.

I've had some discussion about this in email with @jan-hudec

It may also be possible to do something fun with macros.

The parsing of L20n's FTL format needs to be finished. This can probably be replaced by using a parser that is based upon the EBNF specification: https://github.com/l20n/spec/blob/master/grammar.ebnf

The placeholder support for PluralFormat isn't fully hooked up anymore.

I am writing a wrapper for string formatting, so that a string like There are {foo} apples. with an identifier some_string can be accessed like so in Rust:

pub fn some_string(foo: &str) -> String {
    ...
}

Right now it does not seem possible to access Args from anywhere because they are not attached to any struct but generated on the fly by a macro.

What is the suggested course of action for getting access to the Args at the moment? I don't mind if it's a bit round-about, as it will only be used from a build.rs script. Thanks!

The use of HashMap isn't necessary as the number of items in these will usually be quite low, so we can just use a Vec of entries instead and do a quick linear search.