Maja Kądziołka

> With these auto-derives, I'm always hesitant to implement them directly on the type because it can cause collisions with other user defined methods. In this case, the user is...

> 1. This would be a breaking change, which in my mind means there's a higher threshold to reach than simply adding a new feature. I am aware that this...

All things considered, the parameter that matters the most is probably the superblock position. This is how it looks so far: - +0K: FAT12, FAT16, FAT32, HPFS, NTFS, XFS, BFS...

ZFS is interesting - it has some important looking structures starting at 16K, up to 256K, but maybe it's possible to fudge in a "comment" in "Name/Value Pairs" (16-128K) so...

Also interesting is FreeDOS's LEAN filesystem: "The superblock must be stored in one of any sector in range from 1 to 32, inclusive."

Currently the filesystems are entirely independent and don't share data. I want to explore creating some files that would be shared between the two (or more!) filesystems. Naturally, deleting them...

I consider the type-level distinction between "a flag" and "a set of flags" to be a feature. Moreover, your approach wastes space and is useless for any kind of interop...

I'm going off of [the most recent Discord search results for `wait_vram`](https://discord.com/channels/303217943234215948/790920525253836912/874329066273136710). (yes, I'm aware that's not the most authoritative and reliable source :P)

The issue does not seem to be reproducible on either the stable or dev branch, only dev3 is affected. While testing, I noticed a curious difference -- the shell prompt...

Yes, the `$ ` is missing on `dev3`, which is weird but the docs suggest it might be intended?