| {-# LANGUAGE ConstraintKinds #-} | |
| {-# LANGUAGE GeneralizedNewtypeDeriving #-} | |
| module ParserCombinators where | |
| {- | |
| We'll build a set of parser combinators from scratch demonstrating how | |
| they arise as a monad transformer stack. Actually, how they arise as a | |
| choice between two different monad transformer stacks! |
A quick guide to write a very very simple "ECHO" style module to redis and load it. It's not really useful of course, but the idea is to illustrate how little boilerplate it takes.
Step 1: open your favorite editor and write/paste the following code in a file called module.c
#include "redismodule.h"
/* ECHO <string> - Echo back a string sent from the client */
int EchoCommand(RedisModuleCtx *ctx, RedisModuleString **argv, int argc) {
| function transfer | |
| if test (count $argv) -eq 0 | |
| echo "No arguments specified. Usage:\necho transfer /tmp/test.md\ncat /tmp/test.md | transfer test.md" | |
| return 1 | |
| end | |
| ## get temporarily filename, output is written to this file show progress can be showed | |
| set tmpfile ( mktemp -t transferXXX ) | |
| ## upload stdin or file |
My friend Michael Jackson turned off github issues on one of his smaller projects. It got me thinking...
Maintainers getting burned out is a problem. Not just for the users of a project but the mental health of the maintainer. It's a big deal for both parties. Consumers want great tools, maintainers want to create them, but maintainers don't want to be L1 tech support, that's why they
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title>Cross-browser kerning-pairs & ligatures</title> | |
| <style> | |
| body { font-family: sans-serif; background: #f4f3f3; color: rgba(40, 30, 0, 1); width: 500px; margin: 80px auto; padding: 0px; } | |
| a { color: rgba(15, 10, 0, 0.8); text-decoration: none; border-bottom: 1px solid; padding: 1px 1px 0px; -webkit-transition: background 1s ease; } | |
| a:hover { background: rgba(0, 220, 220, 0.2); } | |
| p, li { line-height: 1.5; padding: 0em 1em 0em 0em; margin: 0em 0em 0.5em; } |
For a while, I have felt that the following is the correct way to improve the mass assignment problem without increasing the burden on new users. Now that the problem with the Rails default has been brought up again, it's a good time to revisit it.
When creating a form with form_for, include a signed token including all of the fields that were created at form creation time. Only these fields are allowed.
To allow new known fields to be added via JS, we could add:
| body { | |
| background-color: #002b36; | |
| color: #839496; | |
| font-size: 14px; | |
| white-space: pre !important; | |
| font-family: "Source Code Pro", monospace; | |
| } | |
| .property { | |
| font-weight: bold; |
| Original text here: https://whydavewhy.com/2013/08/16/loyalty-and-layoffs/ |
| extern mod extra; | |
| use extra::json::*; | |
| /* | |
| * This function manages to do absolutely no copying, which is pretty cool. | |
| * | |
| * "What are all those `'r`s?" you ask. Well, they're liftime parameters. They | |
| * indicate how long something lasts (before it's freed). They can't change how | |
| * long something lives for, they only allow you to tell the compiler stuff it |
| # -------------------------------------------------------------------- | |
| # An implementation of Kruskal's algorithm for generating mazes. | |
| # Fairly expensive, memory-wise, as it requires memory proportional | |
| # to the size of the entire maze, and it's not the fastest of the | |
| # algorithms (what with all the set and edge management is has to | |
| # do). Also, the mazes it generates tend to have a lot of very short | |
| # dead-ends, giving the maze a kind of "spiky" look. | |
| # -------------------------------------------------------------------- | |
| # NOTE: the display routine used in this script requires a terminal | |
| # that supports ANSI escape sequences. Windows users, sorry. :( |
