njs12345
Joined 17 years ago
Joined 17 years ago
- Require audit if there is new unsafe code
- Otherwise, rely on cackle to enforce no use of fs/net etc in safe Rust
This could provide the best of both worlds, automating most of the audit burden while still providing strong guarantees.
With an ageing nuclear fleet built mostly in the 70s and 80s France has the cleanest electricity of any country in Europe (except those with abundant hydro).
Perhaps not in safe Rust, but can you provide an example of something Rust can't do that C++ can? It has the same memory model as C++20: https://doc.rust-lang.org/nomicon/atomics.html
We're looking for an experienced Systems Engineer / Site Reliability Engineer to help us deliver high quality software and shape our technical roadmap over the coming years.
The Development department consists of 20 developers across 4 sub-teams: Analysis, Modelling, Systems and Trading. As part of the Systems team, you'll get the opportunity to enhance our DevOps culture, taking our collaboration and automation to the next level. We're on a mission to improve stability and standardisation, and shorten feedback loops in order to make our team more efficient in delivering business value. We're also looking for someone who can help us integrate security considerations into our development process.
Find out more about Football Radar and the role here: https://footballradar.recruiterbox.com/jobs/fk0mg3u/
It still provides a documentation benefit of course.
EDIT: Whoops, yes, as lentil points out, they are indeed distinct types not aliases. So it does provide the benefit of the Rust solution.
The same sort of dogwhistles about 'voter fraud' have been getting airtime in the media as well so I'm sure it won't be long before we have widespread disenfranchisement, just like in the US.
I guess per-tenant you would handle similarly but build some tooling to monitor the state of migrations. It might even be easier in some ways, as you might be more able to take table locks when migrating per-tenant.