effects-examples
cap-std
Our great sponsors
effects-examples | cap-std | |
---|---|---|
10 | 12 | |
405 | 621 | |
1.5% | 1.6% | |
5.8 | 6.6 | |
5 months ago | about 1 month ago | |
OCaml | Rust | |
ISC License | GNU General Public License v3.0 or later |
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.
effects-examples
-
Maybe Everything Is a Coroutine
Isn't a language described very similar to the (future) OCaml with effects (https://github.com/ocaml-multicore/effects-examples) added?
- Examples to illustrate the use of algebraic effects in Multicore OCaml
-
Context: The Missing Feature of Programming Languages
Sure. They probably don't mention coeffects so often because their effect system subsumes both effects (actions to be performed) and coeffects (information from the context), and it can do way more than what you're proposing. Here are some examples you may take a look. The dynamic state example in there could be adapted to act as coeffects (contexts) as you suggest. For coeffects in particular, this is a great resource. You may also be interested in Koka's documentation, as it was designed to be a language with effects and coeffects since the beginning (OCaml did only retrofit them recently).
- Reverse-mode algorithmic differentiation using effect handlers in OCaml 5
-
OCaml Multicore merged upstream
Good question!
https://github.com/ocaml-multicore/effects-examples has links to tutorials and examples for how effects can be used.
There's also some slides from KC's talk on effect handlers https://kcsrk.info/slides/handlers_edinburgh.pdf and materials from the CUFP 17 tutorial: https://github.com/ocamllabs/ocaml-effects-tutorial
https://gopiandcode.uk/logs/log-bye-bye-monads-algebraic-eff... this is also a great introduction
-
Multicore OCaml PR has been merged
Here's a post outlining the part that people are excited about. Here's the examples list if you'd like more concrete examples.
-
Functional Programming Languages Sentiment Ranking
To be honest, though, despite it being cool that OCaml finally has a concrete multicore release date, I'm more interested in the effect handlers. After reading these slides and this article on the topic I realised OCaml getting support for algebraic effects is way more interesting than the parallelism support.
-
Scripting Languages of the Future
I think it's not discussed enough how things like language features shape how library APIs are formed. People usually seem to only consider the question "how would I use this feature?" and not "how would the standard library look like with this feature?", which is surprising given how much builtin libraries affect the pleasantness of a language.
One of the things I'm excited to see is the cap-std project for Rust [0] given what Pony [1] has demonstrated is possible with capabilities. I'm also hoping that languages like Koka [2] and OCaml [3] will demonstrate interesting use cases for algebraic effects.
[0] https://github.com/bytecodealliance/cap-std
[1] https://www.ponylang.io/discover
[2] https://koka-lang.github.io
[3] https://github.com/ocaml-multicore/effects-examples
-
PHP 'noreturn' type RFC accepted, with type name to be 'never'.
Just randomly stumbled upon this example, which is exactly what you were asking about. It is a strongly-typed fork() that uses first-class effects.
cap-std
-
Rust Library Team Aspirations | Inside Rust Blog
I believe you mean capability based, like cap-std.
-
A Performance Evaluation on Rust Asynchronous Frameworks
There might be another reason to prefer async-std right now: the Bytecode Alliance is working on a version of std with support for capability-based security (called cap-std: https://github.com/bytecodealliance/cap-std ), and their async version is based on async-std (called cap-async-std: https://github.com/bytecodealliance/cap-std/tree/main/cap-async-std ). Given the clout that the Bytecode Alliance has, async-std might end up carving a niche out in the Wasm domain.
-
Backdooring Rust crates for fun and profit
Would love to see something like this implemented around creating a Process in cap-std ( https://github.com/bytecodealliance/cap-std/issues/190 )
-
Scripting Languages of the Future
I think it's not discussed enough how things like language features shape how library APIs are formed. People usually seem to only consider the question "how would I use this feature?" and not "how would the standard library look like with this feature?", which is surprising given how much builtin libraries affect the pleasantness of a language.
One of the things I'm excited to see is the cap-std project for Rust [0] given what Pony [1] has demonstrated is possible with capabilities. I'm also hoping that languages like Koka [2] and OCaml [3] will demonstrate interesting use cases for algebraic effects.
[0] https://github.com/bytecodealliance/cap-std
[1] https://www.ponylang.io/discover
[2] https://koka-lang.github.io
[3] https://github.com/ocaml-multicore/effects-examples
- Is using crates more safe than using npm?
-
Why WebAssembly is innovative even outside the browser
I'm not sure you could hack the control flow when running bytecode on the JVM, but I strongly doubt that. (The JVM is "high-level" as pointed out previously and doesn't execute ASM like code. So there is no of the attack surface you have to care on the ASM level).
And capabilities are anyway something that belongs into the OS — and than programs need to be written accordingly. The whole point of the capability-security model is that you can't add it after the fact. That's why UNIX isn't, and never will be, a capability secure OS.
But "sanboxing" some process running on a VM is completely independent of that!
WASM won't get you anything beyond a "simple sanbox" ootb. Exactly the same as you have in the other major VM runtimes.
If you want capability-secure Rust, there is much more to that. You have to change a lot of code, and use an alternative std. lib¹. Of course you can't than use any code (or OS functionality) when it isn't also capability-secure. Otherwise the model breaks.
To be capability-secure you have actually to rewrite the world…
¹ https://github.com/bytecodealliance/cap-std
-
Security review of "please", a sudo replacement written in Rust
The type system could definitely help. There's all sorts of things we can do. One really cool project is https://github.com/bytecodealliance/cap-std
- Preparing rustls for wider adoption
- cap-std: Capability-oriented version of the Rust standard library
-
First class I/O
On the topic of unsafe being used to describe raw file descriptors, on one hand, there is a sense in which file descriptors are pointers, into another memory. They can leak, dangle, alias, or be forged, in exactly the same way. On the other, there is an open issue about this.
What are some alternatives?
eioio - Effects-based direct-style IO for multicore OCaml
godot-wasm-engine
lwt_eio - Use Lwt libraries from within Eio
watt - Runtime for executing procedural macros as WebAssembly
ocaml-effects-tutorial - Concurrent Programming with Effect Handlers
rusty-wacc-viewer
raytracers - Performance comparison of parallel ray tracing in functional programming languages
cargo-supply-chain - Gather author, contributor and publisher data on crates in your dependency graph.
sandmark - A benchmark suite for the OCaml compiler
cargo2nix - Granular builds of Rust projects for Nix
ocaml - The core OCaml system: compilers, runtime system, base libraries
bsnes-plus-wasm - debug-oriented fork of bsnes, with added wasm runtime for scripting