penne
Penne is a pasta-oriented programming language that favors the goto-statement for flow control. (by SLiV9)
repos
By api
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
penne
Posts with mentions or reviews of penne.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-19.
-
What backwards-incompatible changes would you make in a hypothetical Rust 2.0?
There are basically two options: - the (Scopes)[http://scopes.rocks] reference logic - the (Penne)[https://github.com/SLiV9/penne] reference logic
-
Introducing: "goto"
I'm not sure if I first read that article before or after starting Penne (https://github.com/SLiV9/penne), but my main motiviation for the language was definitely a response to the ubiquitous "goto considered harmful" mentality, and wanting to see if goto could be redeemed. And for an alt-history language I think Penne makes use of goto pretty well.
-
'#[must_use]' not being the default on functions goes against "Rust has the safest defaults" principle
Excellent suggestion. I've taken my small compiler project, where I don't usually run clippy, and tallied my findings:
-
Which phases/stages does your programming language use?
My Penne compiler has a lexer that turns source code into tokens and a recursive descent parser that produces a list of "common AST" declarations.
-
Do people hand write predictive parsers?
Here's the source code if you're interested: https://github.com/SLiV9/penne/blob/main/src/parser.rs
- Introducing Penne (v0.2.1), a pasta-oriented programming language that favors the goto-statement for flow control
- How to compile my language for LLVM?
repos
Posts with mentions or reviews of repos.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-19.
-
What backwards-incompatible changes would you make in a hypothetical Rust 2.0?
struct GithubClient { http: H, // .. } #[test] fn test_repo() { let gh = GithubClient::new(httpclient_from_fn(|request| { assert_eq!(request.uri(), "https://github.com/api/repos/rust-lang/rust"); Ok(Response { .. }) })); let repo = gh.get_repo("rust-lang", "rust").unwrap(); assert_eq!(repo.owner, "rust-lang"); assert_eq!(repo.name, "rust"); }
What are some alternatives?
When comparing penne and repos you can also consider the following projects:
turbo.fish - ::<> ⠀ https://turbo.fish/ ⠀ <>::
ligmascript - LIGMAScript (the bestest programming language ever) compiler and interpreter