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
Right now there is a lot of code duplication between Fat32Volume and Fat16Volume types. Since the filesystem type is only known at runtime, everything gets compiled in. It might be better to refactor both into a single type and do the matching internally instead of outside, the downside is that not everything translates between the two, it would need more fields with Option in the struct and probably some more methods would have to be made failable.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Right now there is a lot of code duplication between
Fat32Volume
andFat16Volume
types. Since the filesystem type is only known at runtime, everything gets compiled in. It might be better to refactor both into a single type and do the matching internally instead of outside, the downside is that not everything translates between the two, it would need more fields withOption
in the struct and probably some more methods would have to be made failable.The text was updated successfully, but these errors were encountered: