UCStr::from_ptr_with_nul & inconsistent documentation + behaviors around nulls about widestring-rs HOT 1 CLOSED

Not surprised some inconsistencies have popped up, there was some significant internal refactoring. A PR to correct these would be welcome.

Should I create a PR for UCStr to try and return &[UChar::NUL] for the length 0 case? (Maybe UCStr can gain a Default impl?) Should it scan/truncate too (would change the result of str.len())? Perhaps matching function signatures?

In general, _unchecked methods should not scan/truncate, and methods that are passed a len parameter should scan and error on missing/unexpected nuls depending on signature. Methods that receive only the pointer should scan and truncate without error. This should be true for both UCStr and UCString. Getting the zero length behavior consistent would be useful

from widestring-rs.