An extremely fancy 128×8LUT with arbitrary layers and 2×64bits inputs is still barely 5120 config bytes, 1052368 transistors (13 × layers transistors delay).

One instruction would load the config into a CPLD register.
Then an other would use a CPLD register, two input GP and write to an output GP.

Welcome to the club

👀

K

ELRS Configurator

For some reason I should figure out, when doing a local compilation it writes defines to a userdefines.txt file, but none are applied to the build process and it gives you a binary with all defaults.

I could automate it but it involves plugging the oscilloscope and checking if the SPI CLK line is moving.

I've got an SBC and somewhere between 4.4 and 6.6 one of the SPI bus stopped working, it shows up in `/dev/spidev1.0` but it is electrically mute & deaf.

True altho I've reached a point I never thought I ever would,
there are so many commits `git bisect good` or `git bisect bad` take 5 minutes to complete.
Figuring out a new mid point and checking out the new tree !

Sadly no, this is related to building tsgo itself.
It helps people working on typescript-go like the typescript team.

As a user your typescript bugs might be solved a bit faster this wont happen anymore:

Incremental rebuilds and it would parallelize better.

Idk if it ever use github generated emails.

But yes complete lack of stacked CL is why I moved to gerrit.

Also I can trigger CI or Auto Submit in the push command for the whole patch set.

And funny thing is, 30s is still slow by our standards, 5s hot recompile is where I would be very happy.

But because typescript-go has such enormous packages in comparison to the average go codebase that quite unrealistic.
As any change require rebuilding the complete huge package.