From 2903164ca2f24be1b0cc24631c84334bf4210542 Mon Sep 17 00:00:00 2001
From: Tom Panton <34181656+Pantonshire@users.noreply.github.com>
Date: Fri, 4 Jun 2021 20:37:41 +0100
Subject: [PATCH] Add some plans for the future

---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index 18cda09..17c005c 100644
--- a/README.md
+++ b/README.md
@@ -172,3 +172,7 @@ Here is a table to show which traits you should derive, depending on your enum:
 There are also `ScribeString` and `TryScribeString` traits which can be used in the same situations as `ScribeCowStr` and `TryScribeCowStr`, respectively.
 These traits produce a `String` rather than a `Cow<'static, str>`, so they will always perform an allocation. Therefore, you should prefer the
 `ScribeCowStr` traits over the `ScribeString` traits, unless you *really* don't want to use a `Cow` for whatever reason.
+
+## Plans for the future
+- [ ] Converting to / from types other than strings
+- [ ] Unix-permissions-style encoding for collections of enum variants