Illia Denysenko

In the process of implementing it via FluentValue::Custom and during implementing FluentType for LazyValue, I found that FluentValue doesn't implement FluentType. Shouldn't it? :thinking:

@zbraniecki I thought about implementing percentage formatting, but I'm a bit worried about language-dependent formatting, do you have any advice on how to do it?

> I'd wait for ICU4X NumberFormatter, we have scaffolding for it in https://unicode-org.github.io/icu4x-docs/doc/fixed_decimal/index.html for some aspects, and [unicode-org/icu4x#1441](https://github.com/unicode-org/icu4x/issues/1441) for others. > > Maybe you'd like to help with that? :)...

So, I was trying to create a function for EVAL but lifetimes were stronger than me :) But I was able to add another branch to `ResolveValue` impl (and WriteValue)...

@zbraniecki how feasible would it be to get something like that?

Oh, I just found this proposal which is basically does the same thing https://github.com/projectfluent/fluent/issues/80

Makes sense, yes. Keeping this open, because in theory this problem is still not solved.

(Also I think that using an idea from projectfluent/fluent#80 is better than ad-hoc function, so renamed this issue)

@zbraniecki do you foresee any problems with this?

Well, reading this link, I would say "yes" to both. > Use variants only if the default variant makes sense for all possible values of the selector. > When using...