| namespace RFC where | |
| parseDigit = oneOfChars [?0, ?1, ?2, ?3, ?4, ?5, ?6, ?7, ?8, ?9] | |
| parseHex = Unipar.satisfy isHexDigit "wasn't a hex digit" | |
| parseCRLF = (ch ?\r Unipar.>> ch ?\n) | |
| type RawHeaders | |
| = RawHeaders (Map Text Text) | |
| type Request | |
| = Request HostName Text RawHeaders |
I'm writing this gist for my own records but it might help someone else too.
Support for Catalina has improved a lot since the update was first rolled out.
Note: See the NixOS manual for discussion of the --darwin-use-unencrypted-nix-store-volume option.
| /*bin/echo ' -*- mode:c;indent-tabs-mode:nil;c-basic-offset:2;coding:utf-8 -*-┤ | |
| │vi: set net ft=c ts=2 sts=2 sw=2 fenc=utf-8 :vi│ | |
| ╞══════════════════════════════════════════════════════════════════════════════╡ | |
| │ To the extent possible under law, Justine Tunney has waived │ | |
| │ all copyright and related or neighboring rights to this file, │ | |
| │ as it is written in the following disclaimers: │ | |
| │ • http://unlicense.org/ │ | |
| │ • http://creativecommons.org/publicdomain/zero/1.0/ │ | |
| ╚────────────────────────────────────────────────────────────────────'>/dev/null | |
| if ! [ "${0%.*}.exe" -nt "$0" ]; then |
| #include <stdio.h> | |
| #include <freetype2/ft2build.h> | |
| #include FT_FREETYPE_H | |
| int main() { | |
| FT_Library ft; | |
| FT_Error err = FT_Init_FreeType(&ft); | |
| if (err != 0) { | |
| printf("Failed to initialize FreeType\n"); |
Add on top of default.nix: with import {}; or simply run as nix-build '' (i. e. for nix-build complaining) or rather nix-build -E 'with import {}; callPackage ./default.nix {}' (or even import)
(previous Yoneda blog) (reddit) (twitter)
Let's explore the Yoneda lemma. You don't need to be an advanced Haskeller to understand this. In fact I claim you will understand the first section fine if you're comfortable with map/fmap and id.
I am not out to motivate it, but we will explore Yoneda at the level of terms and at the level of types.
| WAYLAND_PROTOCOLS=/usr/share/wayland-protocols | |
| # wayland-scanner is a tool which generates C headers and rigging for Wayland | |
| # protocols, which are specified in XML. wlroots requires you to rig these up | |
| # to your build system yourself and provide them in the include path. | |
| xdg-shell-protocol.h: | |
| wayland-scanner server-header \ | |
| $(WAYLAND_PROTOCOLS)/stable/xdg-shell/xdg-shell.xml $@ | |
| xdg-shell-protocol.c: xdg-shell-protocol.h |
What is strict aliasing? First we will describe what is aliasing and then we can learn what being strict about it means.
In C and C++ aliasing has to do with what expression types we are allowed to access stored values through. In both C and C++ the standard specifies which expression types are allowed to alias which types. The compiler and optimizer are allowed to assume we follow the aliasing rules strictly, hence the term strict aliasing rule. If we attempt to access a value using a type not allowed it is classified as undefined behavior(UB). Once we have undefined behavior all bets are off, the results of our program are no longer reliable.
Unfortunately with strict aliasing violations, we will often obtain the results we expect, leaving the possibility the a future version of a compiler with a new optimization will break code we th
This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.
While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.
