Jubilee

@RalfJung Yeah, we absolutely need a totally ludicrous amount of tests for floating point assumptions. I am going to be trying to develop such as part of developing portable SIMD....

Can we vary a given Trait impl for two types based on constness? I think I saw an RFC for that, but I do not believe it had achieved acceptance.

Are there any problems with `const fn foo(a: T, b: T) -> T::Output { a + b }` implying `T: const Add` that would prevent making that a blocker? Ergonomics,...

IEEE754-2019 has some recommendations for reproducible floating point results and one of them is that you work with an "arithmetic" float that is also an "interchange" float. That means working...

Pardon? I have evaluated many platforms and have a good understanding of the nuances of float repr. All of them are well-defined by the IEEE754 floating point standard nowadays, because...

I have done some more thought about the very nature of the question presented regarding symbolic math, and the only thing that would make sense for abstract computations on floats...

> > IEEE754-2019 has some recommendations for reproducible floating point results and one of them is that you work with an "arithmetic" float that is also an "interchange" float. That...

> Hardcoded MMIO address stuff > We should define a platform-specific way to do this, possibly requiring that you only use volatile access This should probably be more like `core::arch::asm!`:...

> At least in the bootstrap, the compiler will complain if you allow() a lint in your code that doesn't exist. This potentially just means: Hm... I think we can...

There are several different PNVI models with distinct implications, including ones that the paper did not fully explore, and allusions to other possibilities. Please do not truncate them to merely...