betz47

3 ms·

1. 1.▲
   by betz47 3y ago

   This is our thinking as well, a complete rewrite in another language (short of formally verifying the code) could introduce all sorts of logical bugs that did not exist or were patched in the old code.
2. 2.▲
   by betz47 3y ago

   We chose to start with temporal safety (use-after-free, uninitialised memroy etc) but are going to implement spacial safety (buffer overflows/underflows) soon (See roadmap https://xr0.dev/vision-roadmap ). Xr0 is not li
3. 3.▲
   by betz47 3y ago

   Xr0 is currently targeting the c89 spec and working up from there, thread safety is something that we would address in C11 (See a previous discussion here https://news.ycombinator.com/item?id=39858240#39858813 ).
4. 4.▲
   by betz47 3y ago

   Xr0 currently works this way, the annotations can be stripped out with a "-s" flag (See here https://xr0.dev/learn#compiling )