Tracking issue for owned CString conversions

[alexcrichton]

This is a tracking issue for the into_foo methods being added in #28977. Some possible future questions to consider:

• Is IntoStringError suitable? Named appropriately? Correct set of accessors? etc.
• Should be paired with an Into implementation

[Diggsey]

Relatedly, I think the documentation for CString could be improved: it should make it explicit that CStrings do not have or enforce any specific encoding, they are simply null-terminated arbitrary byte sequences.

On the other hand, all of the conversion methods will implicitly assume that it is supposed to contain UTF8 data (an unfortunate decision IMO, but too late to change). It should therefore warn that the default conversions will not necessarily be what is required: users should look to the documentation of the C library they are interfacing with to determine what, if any, encoding is used for its strings.

[alexcrichton]

🔔 This issue is now entering its final comment period for stabilization 🔔

[BurntSushi]

This looks OK to me. I would like to echo some of @Diggsey's thoughts. In particular, the docs could use improving. e.g., into_string should probably "UTF-8 data" instead of "Unicode data."

[alexcrichton]

The libs team discussed this recently and the decision was to stabilize

[alexcrichton]

Closed by #30943