The canonical way to make a proposal for something to be included in Rust is to write an RFC. This typically gets input from many community members and will get a formal decision deciding whether the specific feature is to be implemented or not.
These are sometimes preceded by a Pre-RFC or even a Pre-Pre-RFC which are typically posted on internals.rust-lang.org but sometimes just linked from internals to a proposal stored in someones fork of RFCs. A serious proposal follows this form and is typically quite thorough and detailed though it isn’t quite unheard of for some to just waive things they don’t know like implementation details by saying “I’m not capable of implementing this” or “I don’t know how it would be implemented.”
If you’d seriously like to try to push this forward, you might want to try writing a Pre-RFC in the standard format and post it. People are more likely to invest time in a serious proposal which effectively tries to motivate and detail your desired feature than a simple inquiry about whether it is feasible and useful.
An easier route would be to file an RFC issue which effectively stores it away until someone decides it’s worth an RFC someday in the future. Then it would actually be under consideration. An RFC gets much more attention than an issue.