TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

RealtimeSanitizer for Rust

84 点作者 Archit3ch4 个月前

5 条评论

jtwaleson4 个月前
Ok so basically they are introducing annotations so that the compiler can reason about the code and warn the programmer for non-realtime usage.<p>When you think about it, it&#x27;s a lot like a type system.<p>I haven&#x27;t worked with realtime systems, but I have other constraints. E.g. I want the memory usage of a function to stay within x kilobytes, or I want an api call to return within a second, or I want to ensure there is no PII being sent to the logs.<p>I sincerely hope that in the future we&#x27;ll have languages that cater to these kind of constraints. Think function coloring on steroids. This way the compiler can help figure out problems and we need way less tests.
评论 #42803453 未加载
评论 #42804306 未加载
评论 #42801980 未加载
nevi-me4 个月前
This looks like it could also be useful in embedded programming, specifically around detecting allocations in platforms that allow them.
Rygian4 个月前
The remark on flagging mutex use was quite interesting. From afar, using mutexes in real-time code seems like asking for ~trouble~ formal validation.
oytis4 个月前
Oh, I hoped it would be able to check timing constraints. In reality it&#x27;s a linter marking known bad function calls.
saagarjha4 个月前
Does this flag loops as well?
评论 #42810474 未加载