rusty-cpp

> The article doesn't show any function lifetime annotations, only @safe and @unsafe. It does, but it's under the "External Annotations" section: // External annotations go in a header file // @external: { // strlen: [safe, (const char* str) -> owned] // strcpy: [unsafe, (char* dest, const char* src) -> char*] // strchr: [safe, (const char* str, int c) -> const char* where str: 'a, return: 'a] // // // Third-party libraries work the same way // sqlite3_column_text: [safe, (sqlite3_stmt* stmt, int col) -> const char* where stmt: 'a, return: 'a] // nlohmann::json::parse: [safe, (const string& s) -> owned json] // } > The where clause specifies lifetime relationships—like where stmt: 'a, return: 'a means the returned pointer lives as long as the statement handle. This lets the analyzer cat

Very cool project! Always happy to see more work around static analysis. However, looking at the recent commits it doesn't quite look like the most solid foundation: https://github.com/shuaimu/rusty-cpp/commit/480491121ef9efec... fn is_interior_mutability_type(type_name: &str) -> bool { type_name.starts_with("rusty::Cell<") || type_name.starts_with("Cell<") || type_name.starts_with("rusty::RefCell<") || type_name.starts_with("RefCell<") || // Also check for std::atomic which has interior mutability type_name.starts_with("std::atomic<") || type_name.starts_with("atomic<") } … which then 30 minutes later is being removed again because it turns out to be completely dead code: https://github.com/shuaimu/rusty-cpp/commit/84aae5eff72bb450... There's also quite a lot of dead code.