hell nawh

Author: AWeirdDev

README.md

@@ -2,6 +2,8 @@
 
 > *(adj.) making great demands on one's skill, attention, or other resources.*
 
+✅ [**Docs**](https://aweirddev.github.io/exacting) and [**PyPi**](https://pypi.org/project/exacting)
+
 `exacting` is a picky dataclass runtime utility collection, making sure all type annotations are followed.
 
 Essentially... **THE** go-to option for dataclasses. heh.
@@ -146,4 +148,4 @@ Woah! That's a lot of code to process. To put it simply, exacting supports:
 
 Kind of, but somehow native performance is way better than Rust. That is, exacting is *generally* faster than Pydantic on a few benchmarks. Woooosh
 
-Anyway, thanks for hopping onto this quick tour, you can [read the docs](https://aweirddev.github.io/exacting) if you'd like.
+Anyway, thanks for sticking with us, you can [read the docs](https://aweirddev.github.io/exacting) if you'd like.

docs/index.md

@@ -9,7 +9,7 @@ Essentially... **THE** go-to option for dataclasses. heh.
 **🔑 Key features**:
 
 - **100% static typing.** Because I hate nothing too.
-- Up to **10x faster** than [`pydantic`](https://pydantic.dev)! (Them: 60ms, us: 6~9ms)
+- Generally **faster** than [`pydantic`](https://pydantic.dev)!
 
 ![static typing](static-typing-proof.png)
 
@@ -95,11 +95,12 @@ Show(
 ??? failure "TypeError: Error while validating…"
 
     ``` python
-    TypeError: 
-    Error while validating dataclass 'Show' at attribute 'name':
-    (isinstance) Expected <class 'str'>, got: <class 'int'>
+    ValidationError:
+    During validation of dataclass Show at field 'name', got:
+      • Expected type <class 'str'>, got <class 'int'>
     ```
 
 Normally, when you use the parameters passed in example (2) above, the Python `dataclasses` library might as well just go with it, because they only put the additional **static typing** to the model, but not at **runtime**. Exacting makes sure that at both times, types are all enforced. It even gives you a detailed error message on where this occurs! (In a cool way)
 
 It's worth noting that error generations are *lazy*, which means once Exacting finds out about a problem about a dataclass, it raises a `ValidationError`. This saves a lot of computation time if you have a larger model.
+

python/exacting/core.py

@@ -87,15 +87,14 @@ class _Dc: ...
 
     class _Dc: ...
 
-    class _Internals: ...
+    class _Internals:
+        def __init__(self, **kwargs):
+            get_exact_init(self)(self, **kwargs)
 
 
 class Exact(_Dc, _Internals):
     """Represents a dataclass with runtime type checks."""
 
-    def __init__(self, **kwargs):
-        get_exact_init(self)(self, **kwargs)
-
     def __init_subclass__(cls):
         dataclass(cls)
 

test.py

@@ -11,22 +11,15 @@ class Show(Exact):
     description: str | None
     actors: list[Actor]
 
+
 # (1) ✅ OK, exacting is happi
 Show(
     name="Severance",
     description="great show",
     actors=[
         Actor(name="Adam Scott", portrays="Mark S."),
         Actor(name="Britt Lower", portrays="Helly R."),
-    ]
+    ],
 )
 
 # (2) ❌ Nuh-uh, exacting is angri
-Show(
-    name=123,
-    description=False,
-    actors=[
-        "Walter White",
-        "Jesse Pinkman"
-    ]
-)