pgo
PGo is a source to source compiler from Modular PlusCal specs into Go programs. (by DistCompiler)
panicparse
Crash your app in style (Golang) (by maruel)
Our great sponsors
| pgo | panicparse | |
|---|---|---|
| 2 | 3 | |
| 167 | 3,483 | |
| 4.8% | - | |
| 3.7 | 0.0 | |
| 24 days ago | 7 months ago | |
| TLA | Go | |
| Apache License 2.0 | Apache License 2.0 |
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.
pgo
Posts with mentions or reviews of pgo.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Is “x' = f(x)” a programming paradigm?
Maybe you'd be interested in PGo, though it's nothing like you asked for ;-), but at least it's in similar domain. They had a talk at the TLA+ Conference.
-
TLA+ in OMSCS?
There are research efforts underway to auto-generate code from TLA+ specifications but they are still in their infancy.
panicparse
Posts with mentions or reviews of panicparse.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-17.
-
how to demangle a Golang crash call stack
Maybe using panicparse helps you understanding the stack traces.
-
Uhoh
We have a similar internal package where we can add per stack variables / context. We use https://github.com/maruel/panicparse to get a structured stacktrace, then append to that, and the whole json blob ships to Sentry. I think it's awesome and has almost completely eliminated any need for logging.
-
Remove source path from Go's panic stack trace
This one works nicely too: https://github.com/maruel/panicparse