Adding no_std support

[pranav-bhatt]

Do you have plans for adding no_std support anytime soon? Thanks!

[svartalf]

I'm not quite sure what do you mean; with no_std we can't assume that network exists at all, and therefore, there might be no such concept as a "hostname" at all.

Can you elaborate more on your case?

[pranav-bhatt]

So I'm working on making the CloudEvents SDK Rust library no_std compatible.

We are thinking of scenarios something like IoT devices running in no_std environments would need to communicate with other devices (I'm sorry if this doesn't make much sense 😅), so your library being able to provide support in such cases would be amazing!

[svartalf]

I don't really see how it would work.

As I said before, having the "network host name" concept in system means that we also have some sort of networking. Being able to compile with no_std by itself does not guarantees that, so unless these imaginary IoT devices conform to some widely used specification for providing API with system information (such as POSIX gethostname) I don't think it is up to this crate to support them.

Let's leave this issue opened in case someone else would want to provide the feedback on this topic.