248 karma · joined February 27, 2012
Alternative is bresenham then for each point iterate a span in the minor axis.
The main issue is that gpr allocation is static and worse case. So on the majority of hardware you hose your occupancy.
It’s the same build system for all of them.
sub => ref = 0
sub => ref = 1
unsub(0)
sub => ref = 1 (two subs with same ref!)Only working on grayscale 16bit images with only the lower 10bits populated I never found it reduced image size. But I was doing per scan adaptive filtering so maybe if I was only allowed one filter for the entire image that would be it?
Just wondering if you did any experiments with different filter strategies?
How does it execute the exact version of clangd that is running on the remote not my local laptop, desktop, or windows machine I’m using to remote in?
How well does it search through files on a slower connection when it has to download every byte of every file?
I don't think this is a particularly good showcase.
which is pretty convenient for this use-case.
It’s “ok”. You can’t do things like re use contexts but it’s perfectly fine for throwing small backends together when you don’t want to force users to install asp runtime. I did a minimal web api around it to make life easier going between it and kestrel.
If kestrel was nugettable without the asp runtime it would be a dream but it requires a lot of that aspcore infra so it is what it is.