From 30f5225002235bed2e4d4877fc71dd6bf4925fec Mon Sep 17 00:00:00 2001
From: Pagwin <git@pagwin.xyz>
Date: Tue, 20 Dec 2022 23:23:12 -0500
Subject: [PATCH] changed article to not draft and added a conclusion

---
 content/blog/rust_type_hiccups.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/content/blog/rust_type_hiccups.md b/content/blog/rust_type_hiccups.md
index e8b94f2..4c4431b 100644
--- a/content/blog/rust_type_hiccups.md
+++ b/content/blog/rust_type_hiccups.md
@@ -6,7 +6,7 @@ description: "A couple of hiccups I've run into with rust's type system"
 
 date: 2022-12-20
 
-draft: true
+draft: false
 
 ---
 
@@ -64,3 +64,7 @@ impl<const km1:i16, const sec1:i16,const kg1:i16,const km2:i16, const sec2:i16,c
 }
 ```
 and had I not run into my type hiccup Mul would've been implemented similarly and Add and Sub would've been trivial. Alas, rust doesn't allow this to compile because `cannot perform const operation using kg1` and so on for all the other const generics... what? What do you mean I can't do a const operation with a const wtf ~~I also got an error that said something about how an associated type wasn't allowed when I set Rhs but shhhhh~~. Yeah in the compiler I imagine that allowing for calculating const generics with values that are const/const generics is relatively easy so I hope that does get improved at some point.
+
+## Conclusion
+
+I like rust's type system and most of the time it does a pretty good job, however when it doesn't work it's annoying. These 2 examples being particularly unsatisfying because they're so natural but oh well hopefully rust is able to make them work in the future.