Rename storage access methods
StorageKey's read and try_read are confusing, notably because of errors related to uninitialized storage.
try_read should be the default behavior and there should be extensive documentation of what happens with the storage initialization.
try_read should be renamed to read and read to read_unchecked, but this is a breaking and abrasive change, so we should consider a way of migrating the interface that doesn't startle the users.
I could happily give it a go.
What about creating in a first place read_unchecked with the content of read in a first release so that there isn't any breaking changes and users can migrate softly. At the same time we could push some deprecation warnings on both try_read ("to be migrated to read in a further release") and read ("functionality was migrated to read_unchecked"). Then, in a further release, we will introduce the breaking changes with try_read --> read.
I think it's a bit more user-friendly (even though that kind of change is always problematic in any case).
Yeah deprecation warnings sounds like a good way to do it.
I am on it then. You can assign me to the issue