Usage in no_std environments about mqttrs HOT 9 CLOSED

Looking forward to a no-std mqttrs :) I think it might even be possible without a feature flag, which would be great.

NonZeroU16 should be nostd-safe.

I don't quite recall what std::fmt is used for; if it's used for error handing then the best thing to do might be to tweak the error types a bit.

Concerning bytes, I'd like to loosen the dependency on it anyway, accepting an Into<Buf> or something even more generic. The bytes crate has changed its API since the async.await release, we should probably update to that, unless we want to keep our MSRV low. https://seanmonstar.com/post/189439210962/http-v02 mentions that they managed to keep using Bytes but don't expose it in the API anymore, we should have a look at how they did it.

The bytes work could probably be a PR on its own, separate of the no-std work. I'd get to it eventually, but not before end of 2020Q1.

from mqttrs.

Sure i would like to explore in that. The primary use case was to build broker just for fun for me.

But, if there is a use case, which there will be, i think this is a good opportunity to get started with it.

from mqttrs.

I will surely look into that. and you are welcome opening PR also. :)

from mqttrs.

That sound great! I can do an initial PR, but i currently don't have the means to actually test the implementation any more than checking it will compile..
I am still just sweeping github for libraries that might be handy for my IoT application development, to get an idea of how much i have left to implement myself.

from mqttrs.

ok. just open an initial PR, then we can take it from where it needs to be by testing and building on top of initial PR.

from mqttrs.

Sounds good! I will give it a go, as soon as i get some time.

from mqttrs.

awesome. thank you.

from mqttrs.

Sounds great! @vincentdephily if you have the time before me, feel free to open an initial PR :)

from mqttrs.

https://github.com/vincentdephily/mqttrs/tree/serde_and_bytes contains an update to bytes, and the changelog for bytes's new version mentions no_std support. I'll make a PR for that branch once I manage to change encode()/decode() signatures to use something like impl BufMut instead of &mut BytesMut.

From there I guess it'll be pretty easy to support no_std, but I won't tackle that myself as I don't have a usecase for or experience with no_std.

from mqttrs.