Kira Whitehouse

Hi there, **Problem statement**: We're using Guardrail to generate client code for a large API surface. We'd like to give the generated client a more explicit name than the auto-generated...

Hey @blast-hardcheese :) Thanks for reviewing my other open issue! I love the 👀 but also would be curious to hear more detailed thoughts. Do you see any issues with...

Would love to use `inventory` with Wasm as well! I'm new to both Rust and Wasm, so I'm not quite following the root issue here, but hoping for some advice...

Hi there! Having typescript support for protovalidate would be fantastic. I noticed in the linked blocker above that `@protobuf-ts` correctly includes `options` in the generated typescript. I was able to...

> > Would you folks be open to adding library functions that don't depend on protobuf-es while that blocker exists? > > No, we are focusing our attention on improving...

Awesome, thanks, I'll check back in on this ticket in Q1!

Reviewing code, it looks like: - Multiplication is managed in [evaluator.rs](https://github.com/json-e/json-e/blob/49e21ebf11271cf9b48c50f725c4633fa74384f6/rs/src/interpreter/evaluator.rs#L90) - Parsing numbers is managed in [parser.rs](https://github.com/json-e/json-e/blob/49e21ebf11271cf9b48c50f725c4633fa74384f6/rs/src/interpreter/parser.rs#L24-L33)

Reproduced in unit tests in https://github.com/json-e/json-e/pull/540.

I don't think this has anything to do with `json-e`. Seems like a core Rust issue with floating point calculations. ``` 414 // This test fails! The result is 561.5999999999999,...

## Options to consider here 1. By default, whenever doing a numerical calculation, make use of a library that helps with precision computing. 2. Introduce a new operation which users...