ChanServ changed the topic of #rust-embedded to: Welcome to the Rust Embedded IRC channel! Bridged to #rust-embedded:matrix.org and logged at https://libera.irclog.whitequark.org/rust-embedded, code of conduct at https://www.rust-lang.org/conduct.html
glitchy has quit [Remote host closed the connection]
glitchy has joined #rust-embedded
sroemer has joined #rust-embedded
sroemer has quit [Changing host]
sroemer has joined #rust-embedded
ska has quit [Ping timeout: 252 seconds]
richardeoin has quit [Quit: WeeChat 4.1.1]
phycrax[m] has quit [Quit: Idle timeout reached: 172800s]
atom_skillz[m] has quit [Quit: Idle timeout reached: 172800s]
_whitelogger has joined #rust-embedded
Mihael[m] has joined #rust-embedded
<Mihael[m]> Does anyone know why it says no Drop when i'm using constants as sizes for arrays?
<Mihael[m]> however in a separate playground, no matter how much i try to simulate the scenario, it can analyze the size
<Mihael[m]> is there some setting i can increase on how deep the r-a goes when looking for calculations of sizes or something?
<JamesMunns[m]> "no Drop" probably just means "this doesn't have drop glue", e.g. it has no actual destructor
<Mihael[m]> JamesMunns[m]: yeah but when i'm inspecting for struct sizes when improving the codebase, the fact this happens is a huge downside 🙁 got any tips maybe?
<Mihael[m]> since one "no drop"
<Mihael[m]> causes the whole structure to be unable to calculate the size
<Mihael[m]> just because of that constant in the array
<Mihael[m]> where if i replace the constant with actual well, number:
<Mihael[m]> but i can't replicate the issue in a playground...
<JamesMunns[m]> "no Drop" probably has nothing to do with calculating sizes, like you said, it's probably just R-A not "understanding" the constant
<JamesMunns[m]> you could open an issue on rust-analyzer
<JamesMunns[m]> "no Drop" probably has nothing to do with calculating sizes, like you said, the issue is probably just R-A not "understanding" the constant
<Mihael[m]> yeah i will, thank you
dirbaio[m] has quit [Quit: Idle timeout reached: 172800s]
dngrs[m] has quit [Quit: Idle timeout reached: 172800s]
<JamesMunns[m]> if you don't mind running some code, you can always use `core::mem::size_of::<MatterMessageHeader>()` and print it at runtime
<JamesMunns[m]> it's not nearly as nice as having it in the editor, for sure
<JamesMunns[m]> but it's also something you could print on startup
<Mihael[m]> yeah i do that with functions and some structures
<Mihael[m]> but since running it on embedded, it's very time consuming
<Mihael[m]> but obviously it'll do for now
KevinPFleming[m] has quit [Quit: Idle timeout reached: 172800s]