ChanServ changed the topic of #rust-embedded to: Welcome to the Rust Embedded IRC channel! Bridged to and logged at, code of conduct at
starblue has quit [Ping timeout: 260 seconds]
starblue has joined #rust-embedded
<re_irc> <gauteh> Hi, are there other debugger than jlink that can do RTT?
<re_irc> <gauteh> I've written up the ocean wave buoy on, firmware and data written in Rust:
radens has joined #rust-embedded
emerent has quit [Ping timeout: 258 seconds]
emerent_ has joined #rust-embedded
emerent_ is now known as emerent
<re_irc> <firefrommoonlight> I can't do it. Guys. I really am tryign with an open mind
<re_irc> <firefrommoonlight> I can't see Async in Rust as anything beyond a virus
<re_irc> <firefrommoonlight> I'm sorry
<re_irc> <firefrommoonlight> I've made an effort for the past 1-2 months
<re_irc> <firefrommoonlight> I can't
<re_irc> <firefrommoonlight> It's poison
<re_irc> <firefrommoonlight> It risks fragmenting the whole lang
<Shell> you're like 2 years late with that criticism. :p
<re_irc> <firefrommoonlight> Hah sorry I deleted
<re_irc> <firefrommoonlight> Kind of drunk atm
<re_irc> <firefrommoonlight> I stand by what I posted, but I shouldn't
<re_irc> <firefrommoonlight> I really _have_ tried
<re_irc> <firefrommoonlight> I think there's 2 futures for Rust, and I will participate in one of them
<re_irc> <firefrommoonlight> I think even if it spreads to most of the dependencies, we can continue using Rust with the part that is clean
<Shell> 2 "futures" ha ha ha
<Shell> realistically, yeah, though. I've got a mostly-sync application which uses some async stuff via block_on functions and... I can tell that's going to be a source of really weird bugs.
<cr1901> I remember reading once- from someone big into async Rust's design- that "one of the reasons Rust went so hard into async APIs was because 'that's where the funding was outside of Mozilla'".
<re_irc> <K900> Honestly, I don't think async Rust is _fundamentally_ broken
<re_irc> <K900> It's definitely kind of janky
<re_irc> <K900> But that's not really a core design issue, it's mostly a diagnostics and borrowck issue
<re_irc> <K900> The core design I think is pretty sound, and the fact that it actually works on embedded is extremely jicen
<re_irc> <K900> * nice
<cr1901> The ppl who did the design of async Rust took _a lot_ of shit over bikesheds like "postfix await". I try not to gripe too much about it (and honestly, I think "async Rust is fine").
<re_irc> <K900> Honestly, postfix await is great
<re_irc> <K900> I wasn't sold on it at first
<re_irc> <K900> But after writing some code with it, I'm 100% converted
<Shell> I thin async Rust is fine too tbh
<Shell> what I don't think is fine is that any library that vaguely touches the network for a second is now async
<re_irc> <9names (> gauteh: yep, any debugger can do RTT. CMSIS-DAP, STLink.
<re_irc> <9names (> if it can read memory, it can do RTT
causal has quit [Quit: WeeChat 3.5]
explore has joined #rust-embedded
bjc has joined #rust-embedded
aspe has joined #rust-embedded
aspe has quit [Quit: aspe]
aspe has joined #rust-embedded
xnor has quit [Read error: Connection reset by peer]
Foxyloxy has quit [Remote host closed the connection]
causal has joined #rust-embedded
causal has quit [Quit: WeeChat 3.5]
causal has joined #rust-embedded
explore has quit [Quit: Connection closed for inactivity]
aspe has quit [Quit: aspe]