The food process relies on the fact that peracetic acid decomposes rather quickly. However, handling the active solution requires great care. It's highly corrosive and toxic.
I would mostly be concerned about the sub-products of peracids reacting with foods. I don't know if there is any studies on this subject.
I have seen a library with a copy of boost in the include folder. Client code is forced to use this outdated version and must avoid transitive dependencies to boost.
Please don't do that.
(u)int8_t have the same problems, including aliasing because they are just alias of (unsigned) char. Sometimes it's nice to have modular arithmetic mod 256, or compact memory layout for eg. count sketches.
If int8_t exists[1], then you know that char is 8 bits[2] and therefore know that char in char + char always promotes to int because int must have at least 16 value bits and a 16-bit int can represent any char value regardless of signedness.
[1] int8_t is not required.
[2] char is the fundamental unit of addressability. sizeof char always evaluates to 1, sizeof int8_t must be non-0, char must be at least 8 bits, and int8_t must be precisely 8 bits, therefore sizeof int8_t == sizeof char and CHAR_BIT == 8.
Depression can be seen as protection mechanism that reinforce rigid thought patterns in order to avoid runaway (psychosis, mania). So anything tiping the balance in the other direction allows to deprogram those behaviors.
I stopped working on LLVM about 2 years ago (give or take), as i now have way too many reports to be able to do any effective patch or design review, or honestly, keep up with the mailing list. I'm also too far divorced from work being done.
(I unsubscribed late last year)
I specifically reviewed and approved the llvm.noalias patches before i stopped, which is why they are marked as accepted by hal, back in 2016.
More than that, i was one of the people who basically showed that !noalias/etc is fundamentally broken and can't be fixed.
Nothing should be blocked on me at this point, and my reviews account is deliberately disabled so that people can't assign/add me to things.
If something is blocked on me, hal certainly hasn't let me know :)
Understood. Sorry, it was not clear to me what was going on. In any case, the fix seems to be blocked on something, as it hasn't landed yet, and it's unclear what.
> For instance, the AGC (like many 1960s computers) didn't have a stack, so you had to keep track of the return address for each subroutine call.
> I managed to get everything to fit in one bank by reusing these 16 words for multiple purposes, but I spent a lot of time debugging problems when a variable clobbered a location still in use.
It could be fun to make a slightly higher level ad-hoc assembly language for solving these problems. For example SSA with basic blocks.
Honestly not bad. About 7 years of use on personal machine, single volume. It simpler than ZFS and allows cheap incremental backups with send/receive.
One year ago I built a RAID56 with 5 used 2TB drives from eBay. Risky move, but it went smoothly so far. It's only for home storage and important stuff is backuped off site anyway.
One Seagate drive died with lots a bad sectors. The replace command took really long even with the "-r" flag (don't read from replaced drive, in theory), so I ended up unplugging the drive and rebalancing from there.
I have high hopes for bcachefs. We have a real need for a modern FS with tiered caches. I backed the project but I don't have the skills or time to help.
Yes, I'm aware of that. Sorry, bad wording. I choose btrfs because it's simpler to setup. It is also lighter on memory for uses on personal machines. I know ZFS can work with less memory but at a performance disadvantage.
I found the need for a plenty of RAM a little overblown for ZFS. My anecdotal experience: I repaired my home file server replacing faulty RAM with 2G stick (because that was only spare piece I had) as a temporary solution. But as it often happens with temporary solutions it lasted longer, for slightly less then two years. Prefetch feature was automatically disabled, but there were no delays which my perception can register. I suppose speed degradation would be visible on heavy-lifting server, but exactly for personal use one doesn't need any special amount of RAM.
