Will

Is the goal to implement the full numerical tower? If so, do you have a checklist of requirements? From skimming [Wikipedia](https://en.wikipedia.org/wiki/Numerical_tower) it seems like `complex` numbers are the only thing...

Cool, so to recap for Steel. | Type | Representation | |-----------------|---------------------------------------| | integer | `isize` or `BigInt` | | rational number | `Rational` or `BigRational` | | real number...

I did a simple test in a few Scheme interpreters and here is what I found for `(exact 2+3i)`: | Scheme | Value | |----------|-------| | racket | #t |...

Since it's going to be boxed anyways, the simplest implementation will probably be a `Gc` that points to 2 non-complex numbers: ```rust struct SteelComplex { re: SteelVal, im: SteelVal }...

# Current Status Some functions are still pending. I expect to get them done by the end of March. Pending: - ✔️ exact-integer-sqrt - floor/ - floor-quotient - floor-remainder -...

Data should be initialized in the "constructor" of your `Process` object. Example: ```rust pub struct Process { left: jack::Port, right: jack::Port, } impl Process { fn new(client: &Client) -> Result...

# Idea High level, this seems to be fine. Feel free to send over a patch with the version bumped to `0.13.0`. # Breaking change Oof, I removed some uses...

How about: ```rust pub struct SinePlot { line_plot: LinePlot, // egui plot jclient: jack::AsyncClient, } ... let sine_plot = SinePlot { line_plot, jclient, } ```

I wish `zig-mode` worked well out the box, but `filladapt-mode` seems to work for me. https://www.emacswiki.org/emacs/FillAdapt

Yeah, restricting some items to owned ports makes sense. For anyone willing to take this up: * `PortSpec` is defined at https://docs.rs/jack/latest/jack/trait.PortSpec.html , it can be extended to determine ownership....