shedskin
miri
shedskin | miri | |
---|---|---|
6 | 122 | |
786 | 4,026 | |
1.4% | 4.0% | |
9.7 | 10.0 | |
2 months ago | 5 days ago | |
Python | Rust | |
GNU General Public License v3.0 or later | 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.
shedskin
-
Are there any programming language that implement both a compiler and an interpreter
Even Shed Skin has Python3 compat now, https://github.com/shedskin/shedskin/releases/tag/v0.9.6
- Shed Skin restricted-Python-to-C++ compiler ported to Python 3
- Shed Skin restricted-Python-to-C++-compiler 0.9.6
-
Python vs C
Just as a side note, you can check out https://github.com/shedskin/shedskin . It 'compiles' some Phyton to C++. Might be handy.
-
OpenAI Codex Python to C++ Code Generator
Anything you can learn or use from Shedskin?
https://github.com/shedskin/shedskin
miri
-
Rust: Box Is a Unique Type
>While we are many missing language features away from this being the case, the noalias case is also magic descended upon box itself, with no user code ever having access to it.
I'm not sure why the author thinks there's magic behind Box. Box is not a special case of `noalias`. Run this snippet with miri and you'll see the same issue: https://play.rust-lang.org/?version=stable&mode=debug&editio...
`Box` _does_ have an expectation that its inner pointer is not aliased to another Box (even if used for readonly operations). See: https://github.com/rust-lang/miri/issues/1800#issuecomment-8...)
-
Bytecode VMs in Surprising Places
Miri [0] is an interpreter for the mid-level intermediate representation (MIR) generated by the Rust compiler. MIR is input for more processing steps of the compiler. However miri also runs MIR directly. This means miri is a VM. Of course it's not a bytecode VM, because MIR is not a bytecode AFAIK. I still think that miri is a interesting example.
And why does miri exist?
It is a lot slower. However it can check for some undefined behavior.
[0]: https://github.com/rust-lang/miri
-
RFC: Rust Has Provenance
Provenance is a dynamic property of pointer values. The actual underlying rules that a program must follow, even when using raw pointers and `unsafe`, are written in terms of provenance. Miri (https://github.com/rust-lang/miri) represents provenance as an actual value stored alongside each pointer's address, so it can check for violations of these rules.
Lifetimes are a static approximation of provenance. They are erased after being validated by the borrow checker, and do not exist in Miri or have any impact on what transformations the optimizer may perform. In other words, the provenance rules allow a superset of what the borrow checker allows.
- Mir: Strongly typed IR to implement fast and lightweight interpreters and JITs
-
Running rustc in a browser
There has been discussion of doing this with MIRI, which would be easier than all of rustc.
-
Piecemeal dropping of struct members causes UB? (Miri)
This issue has been fixed: https://github.com/rust-lang/miri/issues/2964
- Erroneous UB Error with Miri?
-
I've incidentally created one of the fastest bounded MPSC queue
Actually, I've done more advanced tests with MIRI (see https://github.com/rust-lang/miri/issues/2920 for example) which allowed me to fix some issues. I've also made the code compatible with loom, but I didn't found the time yet to write and execute loom tests. That's on the TODO-list, and I need to track it with an issue too.
-
Interested in "secure programming languages", both theory and practice but mostly practice, where do I start?
He is one of the big brains behind Miri, which is a interpreter that runs on the MIR (compiler representation between human code and asm/machine code) and detects undefined behavior. Super useful tool for language safety, pretty interesting on its own.
-
Formal verification for unsafe code?
I would also run your tests in Miri (https://github.com/rust-lang/miri) to try to cover more bases.
What are some alternatives?
codex_py2cpp - Converts python code into c++ by using OpenAI CODEX.
cons-list - Singly-linked list implementation in Rust
pythran - Ahead of Time compiler for numeric kernels
sanitizers - AddressSanitizer, ThreadSanitizer, MemorySanitizer
PyMakeCli - An easy to use C/C++ compiler linker and flagger.
rust - Empowering everyone to build reliable and efficient software.
python-compiler - A Python bytecode compiler written in Python. This repository is now a fork of https://github.com/facebookincubator/python-compiler, upstream is there.
Rust-Full-Stack - Rust projects here are easy to use. There are blog posts for them also.
Pyxell - Multi-paradigm programming language compiled to C++, written in Python.
rfcs - RFCs for changes to Rust
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/