Daniel Hauck

> I think it can be sensible for values to be configured (just overriding the defaults) once and then for justification to be enabled selectively. I totally agree. Even in...

Any updates? Or any way I could help with it (in case it's not a premium rule).

I assume this stems from the fact, that there is a floating point epsilon in cetz defined as exactly that value. One can get around this problem by rescaling the...

The discussion so far is about Windows, but what about Android targets? Is there a way to make it work there?

That would be ideal, yes.

A warning would definitely be useful. For example, I'm currently writing a template that does some automatic layouting and it would be nice to give a warning in case the...

> [After discussing on Discord](https://discordapp.com/channels/665528275556106240/700206072144855091/796943684985552947), [@mehcode](https://github.com/mehcode) and I decided we'll support both options: > > * `sqlx::macros!(driver = "any")` which can also be used to enforce, e.g. `sqlx::macros!(driver = "postgres")`...

Regardless of whether something is exposed as a CLI feature, the maximum iterations being somehow configurable is a good idea, I think. And a first step would be to expose...

Maybe? What I'm looking for is some way to turn `1.000` into `1` and `1.111` into `1.11` with the same settings. Or equally `0.001000` into `1e-3` and `0.001111` into `1.11e-3`....

It looks like it was introduced in commit e7f57483127df5747669ba46d0a033e5fd54cdef: ``` e7f57483127df5747669ba46d0a033e5fd54cdef is the first bad commit commit e7f57483127df5747669ba46d0a033e5fd54cdef Author: Mojtaba Samimi Date: Wed Oct 30 17:20:28 2024 -0400 remove unused...