tom/enumscribe
1
0 Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add some plans for the future

Browse Source
This commit is contained in:
Tom Panton authored and GitHub committed 2021-06-04 20:37:41 +01:00
1 parent 0880156d37
commit 2903164ca2
1 file changed
+4
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4
View File
@@ -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. 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 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. `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