programming-language

When zipping with a product iterator with no arguments (which produces only one output, the empty tuple), it seems the check for zip completion does not handle this case:

julia> for (z,) in zip(Iterators.product())
       @show z
       end
z = ()
ERROR: ArgumentError: tuple must be non-empty
Stacktrace:
 [1] first(#unused#::Tuple{})
   @ Base ./tuple.jl:140
 [2] _pisdone
   @ ./ite

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

We've currently turned them off as they are randomly failing in CI but not locally.

We need to get them fixed in CI and turned back on.

When the user defines an invalid top-level term, the error message should give correct info about what is permissible.

https://github.com/unisonweb/unison/blob/6cbd464c0eae2bd3d0a355e09ffef0a409762086/parser-typechecker/src/Unison/PrintError.hs#L1265

Of course, if we want to bring back the namespace functionality, disregard! 😄

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.