tao
rust-orphan-rules
tao | rust-orphan-rules | |
---|---|---|
11 | 11 | |
1,075 | 180 | |
- | - | |
7.7 | 0.0 | |
8 months ago | over 5 years ago | |
Rust | ||
Mozilla Public License 2.0 | Apache License 2.0 |
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.
tao
-
What backwards-incompatible changes would you make in a hypothetical Rust 2.0?
If you want some prior work on this, I've implemented effect-objects-as-return-values in my own language Tao, using uniqueness types. There's still work to be done, but I think it's sufficient as a proof of concept that this approach is viable without type soup.
- Why does Rust have parameters on impl?
-
What are Rust’s biggest weaknesses?
I've personally found through my experiments working on my language Tao that having effects be a property of the return value and not the function itself is very useful and opens up a lot of doors, like iterators that generate effectful values and more precise control over when side effects occur and in what context.
-
Hey Rustaceans! Got a question? Ask here! (29/2022)!
If you’d like to see some examples of great error messages written by a language with a parser combinator, I recommend you check out tao, which is parsed via chumsky, and provides rust-like error messages with the help of ariadne! I have been fiddling with writing my own language for a while now, and after trying out the alternatives, I found Chumsky to be great to work with, and can not recommend it enough. There are also great examples that you can find in the repo as well!
- Tao: A statically-typed functional language
- Tao: 一种静态类型的函数式语言 (Tao: A statically-typed functional language)
-
Hacker News top posts: Jul 5, 2022
Tao: A statically-typed functional language\ (0 comments)
-
Write your own programming language in an hour with Chumsky
I've been developing both throughout the development of Tao, my own hobby language. It's since developed quite an extensive syntax (see here for an example: https://github.com/zesterer/tao/blob/master/examples/99.tao), so you can count it as evidence that chumsky scales to complex grammars: https://github.com/zesterer/tao
rust-orphan-rules
- Coherence and Orphan Rules in Rust: An unofficial, experimental place for docum
- Conflicting trait implementation, but there shouldn't be
-
Fellow Rust enthusiasts: What "sucks" about Rust?
Well, unless someone comes up with better, compatible rules, the orpan rules are gonna stick around.
-
The langage for the next 40 years of engine dev
Additionally there are other issues with rust currently. Compile time code (ala constexpr) is not up to par with C++20 (not really close). The const generic aren't as powerful as C++20 which added non primitive non type template parameters (though with you stuck with C++14, it actually is significantly better than what you have, again, if you're going to use C++, just use 20). Generics accepting closures is a bit more of an ordeal in rust, compared to C++. Also C++'s Duck Typed templates allow for some uncharacteristically strong typing compared to what is expressible in Rust generics currently. Now, duck typed templates do have major downsides, for example the entire feature of concepts is completely irrelevant in rust, but required for sane DTT type bounds, but they also have major upsides. Rust currently doesn't have "negative trait bounds", basically "This objected does not implement this trait, or std::enable_if> or the equivalent concepts implementation. Rust also doesn't have trait specializations, basically template specialization. Do note all features I've talked about to this point have nightly options, they just are at various stages of being stable/complete. Another issue is the orphan rule, though this is kind of a problem in C++ too in some respects, and that's unlikely to change drastically, since there are legitimate reasons for it's existence. For a lot of code none of these things are big deals, others they are, which is why you find inconsistent feed back on these issues.
-
What are Rust’s biggest weaknesses?
Not that simple... hence why Orphan rule is still in-place. The struct wrapper was implemented in Rust as a temporary safe work-around. However, they are making progress on a solution: https://github.com/Ixrec/rust-orphan-rules/issues/1
-
Hey Rustaceans! Got a question? Ask here! (46/2022)!
That's still not an entirely complete explanation because there's more nuanced situations which aren't completely foreign but are foreign enough that if allowed, two crates could write the same impls. Some of the definitions are still unofficial as far as am I'm aware. For the best reference I’ve seen so far see this for more details.
-
Design Patterns with Rust Types
In our crate the compiler doesn't know when calling MyTrait methods on MyStruct whether to use the implementation defined in crate 3 or crate 4! Rust has a set of orphan rules to prevent this situation from happening.
-
De/serialize an external crate's struct
Sadly because of the rusts orphan rule you cannot implement a Trait on a Type where you do not own one or the other. So, apart from upstream contributions your only options are either a new Trait or a new Type.
-
Is the orphan rule the only solution?
If anyone is looking for additional background about orphan rules, check out https://github.com/Ixrec/rust-orphan-rules
- Methods for Array Initialization in Rust
What are some alternatives?
statix - lints and suggestions for the nix programming language
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
pollster - A minimal async executor that lets you block on a future
pom - PEG parser combinators using operator overloading without macros.
keepass-rs - Rust KeePass database file parser for KDB, KDBX3 and KDBX4, with experimental support for KDBX4 writing.
mlton - The MLton repository
dislike-in-rust - A list of the few things I don't like about rust
owo - Export your OneNote note collection to Obsidian, Logseq, Org Mode or any other plain text note-taking app! [Moved to: https://github.com/alopezrivera/OneNoteExporter]
getrandom - A small cross-platform library for retrieving random data from (operating) system source
chumsky - Write expressive, high-performance parsers with ease.
rust-delegate - Rust method delegation with less boilerplate