Dumping some code from ~May 2022. Intended to accompany blog post or something.

An example project where Rust code prints the length of an uploaded file.

Run python3 -m http.server (or equivalent: https://gist.github.com/willurd/5720255), then access http://[::]:8000/

Writing a "pdf file object parser". Starting with parsing individual objects. There are 8 types of objects:

We will also need to parse

Indirect Object definitions (12 0 obj)
Indirect object references (12 0 R),
File structure: Header, body, cross-reference table, trailer.

Some notes:

It can now round-trip (objects, not yet an entire PDF file) via JSON. That is, if you dump to JSON and read back, you will get the exact same bytes.
- This is not as big a deal as it sounds, because we could in principle dump the sequence of bytes into JSON as an array of numbers. However, here we're doing slightly more than that.
Assumes the input is valid, e.g. does not check in dict for unique keys, does not check for stream length, etc.

Status currently:

Out of 19560 PDF files I have, this works correctly for 8724 of them.
As of 2022-04-30 (970471e): Works for 19262 out of 19560 files. So fails for 298 (not all of which are actually PDF files).
As of 2022-05-01 (child of 970471e): Works for 19430 out of 19562 files. So fails for 132 files.
As of 2022-05-01 (after deleting some dupes): Works for 19382 out of 19493 files. So fails for 111 files.
As of 2022-05-01 11:52: Works for 19420 out of 19493 files. So fails for 73 files.
As of 2022-05-01 14:20 (e54b45e): Works for 19426 out of 19492 files. So "fails" for 66 files. Looked at each of them. They are all malformed in some way or the other.

I just read Coping strategies for the serial project hoarder by Simon Willison (simonw), which recommends writing everything down, working issue-first (create an issue, talk to yourself, etc) and basically leave things in a sane state that you can walk away from at any point, so that there isn't any guilt. Sounds like a great state to aspire to!

The first step would be to document what already exists, from a POV of "if I don't do any more work on this project, whatever already exists should still make sense".

Dumping some code from ~May 2022. Intended to accompany blog post or something.

Related tags

Overview

You might also like...

Minimalist multi-track audio recorder which may be controlled via OSC or MIDI.

Sample code of Yew (0.18). Something like a PuyoPuyo.

Code examples for https://www.poor.dev/blog/terminal-anatomy/

Cassette A simple, single-future, non-blocking executor intended for building state machines.

🤖 brwrs is a new protocol running over TCP/IP that is intended to be a suitable candidate for terminal-only servers

Programming language from down under, inspired by this Reddit post.

💫 Small microservice to handle state changes of Kubernetes pods and post them to Instatus or Statuspages

xcp is a (partial) clone of the Unix cp command. It is not intended as a full replacement

A cross-platform Mod Manager for RimWorld intended to work with macOS, linux and Windows

A Supra + Pandoc post-processor for footnote cross-references.

Command-line HTTP client for sending a POST request to specified URI on each stdin line.

Rosenpass is a formally verified, post-quantum secure VPN that uses WireGuard to transport the actual data.

Apply a pixelation effect to any Bevy mesh or scene without post-processing.

convert images to ansi or irc, with a bunch of post-processing filters

Simple and minimalist forward auth service intended for use with reverse proxies (Traefik, Caddy, nginx, etc)

An handy tool that is intended to help your inventory cleanup or dump.

Minimal Bitcoin wallet intended for teaching rust-bitcoin

LSP inline hints for Lua, intended for use with Neovim.

A blazinlgy fast 🚀 transpiler written in rust 🦀 that fixes (pun intended) your problems

Comments

Document everything

Owner

Shreevatsa

Ointers is a library for representing pointers where some bits have been stolen so that they may be used by the programmer for something else

Code for blog post "{n} times faster than C, where n = 128"

Something something B language.

A demo blog post engine in Rust, using Rocket and MongoDB

A utility written in Rust for dumping binary information out of Mach-O files inspired by objdump

Rust-blog - Educational blog posts for Rust beginners

This is a small demo to accompany the Tauri + Yew tutorial

A tetris game I wrote in rust using ncurses. I'm sure that there's a better way to write a tetris game, and the code may be sus, but it techinically works

TCP is so widely used, however QUIC may have a better performance.

A Rust library for evaluating log4j substitution queries in order to determine whether or not malicious queries may exist.