cyclone
BorrowScript
cyclone | BorrowScript | |
---|---|---|
7 | 9 | |
1 | 1,432 | |
- | - | |
10.0 | 5.5 | |
about 10 years ago | 6 months ago | |
C | HTML | |
GNU General Public License v3.0 only | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cyclone
-
Maestro: A Linux-compatible kernel in Rust
One of the inspirations for Rust, as I recall, was Cyclone: https://cyclone.thelanguage.org/
Which was/is a "safe" dialect of C; basically C extended with a bunch of the stuff that made it into Rust (algebraic datatypes, pattern matching, etc.) Though its model of safety is not the borrow checker model that Rust has.
Always felt to me like something like Cyclone would be the natural direction for OS development to head in, as it fits better with existing codebases and skillsets.
In any case, I'm happy to see this stuff happening in Rust.
-
C for All
It sounds like they re-invented Cyclone.
https://cyclone.thelanguage.org
-
Is it possible to have a superset of the C programming languages standard that is as safe as Rust?
Looks like it was a research project and is now abandoned: http://cyclone.thelanguage.org
-
Need to learn FAST... Any recommendations for a free interactive rust course?
The borrow checker is Rust's secret sauce. It's the one thing no other language has. (Except Cyclone I think, which is an unmaintained research language.)
- What do you think about a C transpiler?
-
Is my method of programming wrong?
Also, lifetimes are not the mechanism by which Rust ensures safety - it's a necessary side-effect of the approach that Rust has taken, and this has nothing to do with the issues that "plague" other languages. Region-based memory management techniques are neither new nor really innovative. https://cyclone.thelanguage.org/, which directly inspired Rust, had them, and the authors gave up working on it because the ergonomics were terrible, as is the case with Rust. Lifetimes are needed for the Rust compiler to reason about what it can reasonably allow at compile time, but it, along with the Borrow Checker (which provides the actual safety net) ensures that whole swathes of valid programs are disallowed because the Rust compiler is not smart enough (and probably never will be) to check that these programs are valid.
- A Formal Model of Checked C
BorrowScript
- TypeScript Without Side Effects
-
Is it possible to have a superset of the C programming languages standard that is as safe as Rust?
You might be looking for something like https://github.com/alshdavid/BorrowScript
-
Why are systems languages always overly complex?
I think AssemblyScript is the best example.
Adding the borrow checker is quite invasive though. This guy is trying https://github.com/alshdavid/BorrowScript.
I think it's a kind of fun constraint that experienced and bored devs like to challenge themselves with - the borrow checker. The latest obsession. You absolutely don't need a borrow checker, just like you didn't need everything to be functional programming, but it's intellectually stimulating.
-
TypeScript as Fast as Rust: TypeScript++
Sounds like BorrowScript, which is TypeScript syntax, a Rust borrow checker, and Go-like coroutines. It's designed for wasm and web api targets. (not compatible with TypeScript though)
https://github.com/alshdavid/BorrowScript
-
High level overview of the algorithm steps of Rust's borrow checker?
I asked how to implement a "borrow checker" in JavaScript in my initial attempts (I've learned a decent amount since), which led me to randomly finding BorrowScript that seems to have another implementation I think, so going to be taking a deeper look there for inspiration as well. But if one could explain the steps of the algorithm, and how it integrates/relates with the type inference process, that would be of great use. Not for learning how to use Rust, but to learn how this aspect of its compiler works.
- Rust-inspired borrow checker, TypeScript-inspired syntax
- BorrowScript: TypeScript with a Borrow Checker
- BorrowScript (spec) – Combining the Rust borrow checker with TypeScript syntax
- BorrowScript spec – Combining the Rust borrow checker with TypeScript syntax
What are some alternatives?
cyclonic - WIP port of cyclone to modern platforms
Mezzano - An operating system written in Common Lisp
cedro - C programming language extension: Cedro pre-processor
lobster - The Lobster Programming Language
cake - Cake a C23 front end and transpiler written in C
swc - Rust-based platform for the Web
cyclone
ValueScript - A dialect of TypeScript with value semantics.
checkedc-clang - This repo contains a version of clang that is being modified to support Checked C. Checked C is an extension to C that lets programmers write C code that is guaranteed by the compiler to be type-safe.
DMDScript - An implementation of the ECMA 262 (Javascript) programming language
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
Kind - A next-gen functional language [Moved to: https://github.com/Kindelia/Kind2]