Kendall

@soraros I've opened a new [pull request](https://github.com/modular/max/pull/4425). Thanks!

If I understand this correctly, we want to import `UInt128` from `stdlib/builtin/simd.mojo` and change all of the references to `_UInt128` in `stdlib/builtin/_format_float.mojo` to `UInt128` while also removing the `_UInt128` struct...

> > If I understand this correctly, we want to import `UInt128` from `stdlib/builtin/simd.mojo` and change all of the references to `_UInt128` in `stdlib/builtin/_format_float.mojo` to `UInt128` while also removing the...

@JoeLoser I've created a pull request for this [here](https://github.com/modular/modular/pull/4680), but there needed to be a couple of adjustments to functions in order to account for the change to UInt128. With...

@soraros thank you for being willing to answer questions! For the first bullet point, with `_UInt128` being a struct that holds two `UInt64` values named `high` and `low` would I...

@soraros Hello again, after scoping this I have a couple of questions: 1. Being that `UInt128` is an alias for a SIMD scalar `SIMD[uint128, 1]`, in order to add a...

@soraros I think the idea for `_uint128_low` and `_uint128_high` are great! I'll take a first pass at those and push to my PR branch.

Hello @soraros, I've converted https://github.com/modular/modular/pull/4680 to a draft, reverted the previous changes, and took an initial attempt at `_utin128_low` and `_uint128_high`. I haven't worried about implementing yet, so the commits...

@soraros `cache_f64` now has `_uint64_to_uint128` that takes a pair of `UInt64`'s to construct a `UInt128`. We should be in a place where we can replace `.high` and `.low` with `_uint128_low`...

@soraros I've replaced `.low` and `.high`, but I'm having some trouble understanding how our `_uint128_low` and `_uint128_high` will work with with `_umul192_upper128`. Any initial thoughts upon looking at it?