Transistors aren't free (as in power consumptions, thermal etc), and wasting them on implementing 1 byte granularity TLBs would probably be a hard sell, even if assuming everything can indeed be done in parallel.
A very good read, thanks for taking the time to put pen to paper and sharing the little useful scripts and tricks. There's a world of heavy-handed hacking out there to use. I used to build hundreds of patched kernels or glibcs to simulate complex systems behaviour (failing read()/write(), incomplete fsync, syscalls in general or the network stack erroring out in all possible ways...) and scenarios of those. Happy to see this explained so simply.
Not the UK at least, as someone who has done a completely in-country switch from student to skilled worker. In fact you are not allowed to leave the country when your application is in progress (leaving would cancel it).
Rust works pretty well with C, and you could use cbindgen[0] to generate c headers for rust functions marked as extern and it would work when linked together. However, rustls doesn't seems to be providing any such function. Most of its API is rust-based, using stuff that isn't directly available in C (Option, Vec, etc.). So you would have to write at least some rust code that calls the library, and have your C code calls the rust code that you write.
On the flip side, calling C code in rust is pretty easy - you have the entire libc available, and rust-bindgen[1] generate bindings for you, which in my experience works very well. So, you may also consider writing your program in rust… If that's possible.
