<re_irc>
<@krensito:matrix.org> I guess you need the borrow feature?
<re_irc>
<@krensito:matrix.org> Maybe you can submit a feature request to tinyvec_string. As far as I understand, this crate more ore less wraps tinyvec. So maybe they can implement a slice backed string.
<re_irc>
<@jordens:matrix.org> ckrenslehner: I would need "SliceString".
<re_irc>
<@jordens:matrix.org> Sure. I had "SliceString" mostly written already.
<re_irc>
<@ryan-summers:matrix.org> : This is basically what we were discussing Friday. Heapless-like primitives (VEC and string) that use borrowed buffers instead
<re_irc>
<@ryan-summers:matrix.org> Could be a nice crate
<re_irc>
<@jordens:matrix.org> ckrenslehner: Thanks for the pointers!
emerent has quit [Ping timeout: 244 seconds]
emerent has joined #rust-embedded
<re_irc>
<@tr09:matrix.org> Hi all,
<re_irc>
Anyone knowledgeable with *smoltcp*? I’ve implemented a smoltcp::phy::Device and basically have a copy of examples/client.rs, but TxToken consume is never called. Must RxToken consume really return something (as it is called on repeat) or have I made a mistake in app layer?
<re_irc>
(Alternatively, maybe I’m not even supposed to send these bytes down UART to a EC25’s PPP connection…)
<re_irc>
<@dkhayes117:matrix.org> Is there a way to define a feature flag where that flag has options it must choose from? Or is it better to have a feature-flag/environment variable tag team? IE "trace" flag and "level" options.
<re_irc>
<@dngrs:matrix.org> : unfortunately no
<re_irc>
<@dkhayes117:matrix.org> Well that stinks
<re_irc>
<@dngrs:matrix.org> you can work around it by writing custom "cfg" logic, I think has done that, but it's work
<re_irc>
<@dkhayes117:matrix.org> I noticed that embassy-executor had what looked like a work-around for arch