You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there appears to be no way to choose between 9p2000 or 9p2000.L. There appears to be residual code from possibly an earlier time which suggests there used to be support for 9p2000.
Are there any suggestions on how this should be organized and accessed?
Do we need rust-9pL and rust-9pu and rust-9p?
Do we use different internal modules for each 9p version?
Do we use an enum and have the behavior changed on which is passed? (Most common solution)
The text was updated successfully, but these errors were encountered:
In 2015 when I started developing rust-9p I thought it would be a great idea to support all the variants of 9P.
However, (honestly I'm not quite sure what it was but), as implementing them in a clean way was not so easy I stopped the further developing of other variants other than 9P2000.L cuz I was like who the hell wanna use bare 9P and 9P2000.u when we have 9P2000.L?
Do we need rust-9pL and rust-9pu and rust-9p?
Definitely not.
Do we use different internal modules for each 9p version?
Possibly?
Do we use an enum and have the behavior changed on which is passed? (Most common solution)
Hmm... maybe?
Each 9P variant has the different semantics.
I think Filesystem trait is the thing needed to be worked on to support all the variants because the version negotiation in Filesystem::rversion should be done by library users.
Currently there appears to be no way to choose between 9p2000 or 9p2000.L. There appears to be residual code from possibly an earlier time which suggests there used to be support for 9p2000.
Are there any suggestions on how this should be organized and accessed?
Do we need rust-9pL and rust-9pu and rust-9p?
Do we use different internal modules for each 9p version?
Do we use an enum and have the behavior changed on which is passed? (Most common solution)
The text was updated successfully, but these errors were encountered: