Edmund Lam

Current build command: `g++ -std=c++20 -lsvlang tools/slang/rename/pass.cc /home/slang/build/lib/*.a -lfmt -lmimalloc -lpthread`

Oh my god this isn't an approach I had considered at all... What a solution! I'll definitely try it out, thanks! I think the labeling idea might still have some...

Yeah, I was also thinking maybe we could do something like copying over some of verilog's built in math functions [listed here](https://www.chipverify.com/verilog/verilog-math-functions) for example, or maybe even doing something like...

Getting started on working on this now, but in terms of using functions in the liveness of ports, I think it might be worth considering having some flag in custom...

This still likely won't solve the issue though, because, for example, if `Const` has requirements for its parameter values, we have to find a binding that satisfies these constraints, and...

This is just a test using `floor`, but we can imagine that in the `FFT` with twiddle factors that we would want to do something similar but with `f32_bits(sin(1/n))` to...

Spoke to @rachitnigam about this in a meeting. We decided that in order to have a working solution, floating point parameters can never appear in typechecking expressions. This means expressions...

> * [ ] Easier bit slicing, like `in[2:0]` instead of using `Slice` which can be a bit hard to read Not sure if this should be done (yet); seems...

Never mind, looks like the bug was an issue with the `zero` check.

Just found an issue with all FP add implementations as well: `-1 + 1` results in `1`.