js-proposal-algebraic-effects
ez
Our great sponsors
| js-proposal-algebraic-effects | ez | |
|---|---|---|
| 3 | 2 | |
| 167 | 11 | |
| - | - | |
| 0.0 | 2.7 | |
| almost 3 years ago | 3 months ago | |
| JavaScript | Go | |
| - | MIT License |
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.
js-proposal-algebraic-effects
-
Proposal: Signals as a Built-In Primitive of JavaScript
I have to admit: you're perfectly right here. React of course always relied on mutable state in it's implementation – just so we don't have to. I derailed a lot here to keep this funny thread going ;) I'm still not with you on your definition of "functional", since you treated it synonymously with "purely functional". Functional means just made by applying and composing functions, and react UI is created exactly like that. There is an awesome algebraic effects proposal[1], which will hopefully will be added to JavaScript one day, then react will make use of it to become purely functional.
1: https://github.com/macabeus/js-proposal-algebraic-effects
-
Letlang, a programming language targetting Rust - Road to v0.1
Super interesting, there is a proposal to add this to JavaScript and several languages that use this, unison, koka & eff. I had no idea this was even a thing!
-
Go Replaces Interface{} with 'Any'
Ok I was wrongly assuming that panic was expecting an error type, in fact it's an interface{}.
> Your use of exceptions for flow control (i.e. goto) is considered harmful
Exceptions are a way to delegate error handling to the caller by giving them informations about the unexpected behavior. It implies that the expected behavior is the "happy path" (everything went well) and any deviations (errors) is unexpected.
This is far from a goto because you can have `try/finally` blocks without catch (or defer in golang).
Also, exceptions are just a kind of algebraic effects that do not resume. There was a proposal to JS for this: https://github.com/macabeus/js-proposal-algebraic-effects
This is also easier to test. assertRaises(ErrorType, func() { code... })
Almost every Go library I've seen just return an error (which is just a string), you'd need to parse it to assert that the correct error is returned in special conditions.
ez
-
Show HN: Error return traces for Go, inspired by Zig
While from a first instance, this package seems a bit overkill, I think the idea is interesting and is something that can be improved for Go.
I also felt that Go errors where too bare-bones, so I developed a small package (https://github.com/Vanclief/ez) based on an awesome post that I saw here once. I use this package in all Golang code I touch.
-
Go Replaces Interface{} with 'Any'
I used to really hate that. After reading this amazing post https://middlemost.com/failure-is-your-domain I created a module that makes this bearable https://github.com/Vanclief/ez
What are some alternatives?
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍
errtrace - An alternative to stack traces for your Go errors
exhaustive - Check exhaustiveness of switch statements of enum-like constants in Go source code.
errors - Simple error handling primitives
rustic_result - Result monad for Elixir inspired by Rust Result type