programming-language

It might be useful to have rationalize(x) return x if x is already rational, to allow generic code that takes both reals and rationals as inputs.

OpenZeppelin is currently working on a base-64 library (OpenZeppelin/openzeppelin-contracts#2884) and it turns out that our optimizer is not yet good enough to get to the level of hand-optimized assembly in that case. We should add this code as a test case so that we can use it to evaluate our optimizer improvements.

In the PR and its comments you'll find versions of the

So currently, install in our "unix" Makefile isn't hooked into cmake so it can lead to errors.

in particular if you do

make configure arch=not-our-default
make build
make install

you will end up with a broken install because the arch override from configure is used during build but isn't used during install, instead a different arch (our default) is used and you end

.> names #7pjlvdu42gmfvfntja265dmi08afk08l54kpsuu55l9hq4l32fco2jlrm8mf2jbn61esfsi972b6e66d9on4

  😶

  I couldn't find anything by that name.

.> view #7pjlvdu42gmfvfntja265dm

  #7pjlvdu42g : '{g} t -> Doc
  #7pjlvdu42g a = Special (EvalInline (term a))

I'd expect it to say something like:

I found that hash in your codebase, but it doesn't have any names.
Try `view 

Motivation

The Non-Realtime Synthesis guide (https://doc.sccode.org/Guides/Non-Realtime-Synthesis.html) currently doesn't contain much info or examples that make use of busses and synth mapping/lfo mapping.

Description of Proposed Feature

Add info ala the examples here:
https://scsynth.org/t/how-to-allocate-busses-in-nrt-mode/

i) offsetLeft / offsetRight
ii) layerX / layerY
iii) offsetX / offsetY
These three things really helps in DOM manipulation. It is very cumbersome to do things without these methods. It will bring developer happiness hopefully.