RESTful HTTP API wrapper for cgminer
A fast linearizability checker
Injecting debug without rewriting chain-calling code
API tester and debugger for your CLI
A highly parallel Perl 5 interpreter written in Rust
AI/Human task management system with file-based storage
Rust task runner and build tool.
A Rust implementation of Bitcask, usable as a binary or a library.
CKB RPC server
Compiles bullet3 and exposes rust bindings to the C API
Compiles bullet3 and exposes rust bindings to the C API
Compiles bullet3 and exposes rust bindings to the C API
Adds method pd (Puts Debugging) to Ruby. Defined in Kernel module which is included into Object class so this method is accessible from everywhere
Debuggers are great! They help us troubleshoot complicated programming problems by inspecting values produced by code, line by line. They are invaluable when trying to understand what is going on in a large application composed of thousands or millions of lines of code. In day-to-day test-driven development and simple debugging though, a puts statement can be a lot quicker in revealing what is going on than halting execution completely just to inspect a single value or a few. This is certainly true when writing the simplest possible code that could possibly work, and running a test every few seconds or minutes. Problem is you need to locate puts statements in large output logs, know which file names, line numbers, classes, and methods contained the puts statements, find out what variable names are being printed, and see nicely formatted output. Enter puts_debuggerer. A guilt-free puts debugging Ruby gem FTW that prints file names, line numbers, class names, method names, and code statements; and formats output nicely courtesy of awesome_print. Partially inspired by this blog post: https://tenderlovemaking.com/2016/02/05/i-am-a-puts-debuggerer.html (Credit to Tenderlove.)
Tool to print out data encapsulated in hashtags to the server logs.