ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #crystal
Crystal macros let you generate getter methods at compile time, keeping code DRY while preserving static type safety.
Learn how to build a type‑safe CLI in Crystal using OptionParser. This guide covers flag parsing, positional arguments, error handling, and verification steps to ensure a reliable command‑line tool.
Learn how Crystal’s JSON::Serializable macro generates to_json/from_json methods, when to use annotations, and what trade‑offs to consider.
Crystal replaces Ruby's runtime metaprogramming with compile-time macros. Here's how JSON::Serializable and a small getter-generating macro work, what they cost, and how to verify expansions.
Learn how to diagnose and resolve NilRuntimeErrors in Crystal. This guide covers the use of --warn nilable, safe navigation with .try, and implementing robust nil guards.
Explore how Crystal's type inference provides the speed of a compiled language with the clean syntax of Ruby, including nil-safety.
When deploying a Crystal service, the language itself does not provide built‑in mechanisms for sandboxing or privilege dropping, so security relies on the surrounding operating system and deployment configuration. The goal is to run the compiled binary with the minimal set of permissions needed for its function—such as read‑only access to specific directorie
Conservative Garbage Collection in Crystal Crystal relies on the Boehm-Demers-Weiser conservative garbage collector to manage heap memory. Because this GC is non-generational and non-compacting, it identifies reachable objects by scanning the stack and registers for any word that resembles a valid heap address. Heap Retention Uncertainty In applications util
A Crystal application compiled with crystal build --release functions as expected in a local development environment but fails to execute when deployed to a production server with a different Linux distribution. Because Crystal compiles to LLVM IR and links against system libraries, the resulting binary is platform-specific. Discrepancies between the GLIBC v
json
llvm