Initial import

.github/workflows/test.yml

@@ -0,0 +1,22 @@
+name: Tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Install Rust
+        uses: actions-rs/toolchain@v1
+        with:
+          toolchain: stable
+          profile: minimal
+          override: true
+      - name: Run tests
+        run: cargo run

.gitignore

@@ -0,0 +1 @@
+/target

Cargo.toml

@@ -0,0 +1,18 @@
+[package]
+name = "merde_json"
+version = "0.1.0"
+edition = "2021"
+authors = ["Amos Wenger <[email protected]>"]
+description = "Serialize and deserialize JSON with jiter and declarative macros"
+license = "Apache-2.0 OR MIT"
+readme = "README.md"
+repository = "https://github.com/bearcove/merde_json"
+keywords = ["json", "serialization", "deserialization", "jiter"]
+categories = ["encoding", "parser-implementations"]
+
+[dependencies]
+jiter = "0.5.0"
+
+[dev-dependencies]
+serde = { version = "1.0.204", features = ["derive"] }
+serde_json = "1.0.121"

README.md

@@ -0,0 +1,14 @@
+# merde_json
+
+Do you want to deal with JSON data? Are you not _that_ worried about the
+performance overhead? (ie. you're writing a backend in Rust, but if it was
+written in Node.js nobody would bat an eye).
+
+Are you tired of waiting for proc macros to compile, and dealing with super
+generic traits?
+
+Do you not care about any formats other than JSON?
+
+Are you ready to give up the comforts of `#[serde(rename_all)]`, `#[serde(flatten)]`, etc.?
+
+Then the bag of compromises known as `merde_json` might just work for you!