Closed chipsenkbeil closed 1 year ago
And we'd need Utf8 versions of WindowsComponent
, WindowsComponents
, UnixComponent
, and UnixComponents
.
Nearly done. The implementations and majority of tests are committed, but some additional conversions need to be added.
It's been awhile since I've touched this library and I cannot remember what else needed to be done with the conversion logic. So for now I'm going to publish the v0.2 release and additions can be made as needed.
Right now, the
Path<T>
andPathBuf<T>
types use raw[u8]
andVec<u8>
underneath. It would be nice to haveUtf8Path<T>
andUtf8PathBuf<T>
that usestr
andString
as an alternative.The encoding and parsing logic would work without needing any changes since we can get the bytes for the
str
andString
. It would mean adding another entire copy of the structs and enums forIter
,Ancestors
,Display
,Path
, andPathBuf
. Will also need custom versions forWindowsPrefix
andWindowsPrefixComponent
.