Skip to main content

Search

Items tagged with: Rust


We're looking for a #c / #cpp or #rust #freelance developer! It's mostly about Linux namespaces, PAM modules, and patches in 3rd-party software. Low volume. Take a look, mail us, or spread the word!

blog.uberspace.de/freelance-jo…

Boosts very welcome! #rustlang #jobad #job


Or in Lisp: (cons cat (cons cat nil))

In Rust: Box<(Cat, Box<Cat>)>

#lisp #rust #RustLanguage


Live in 30 minutes: live coding #Rust for #Matrix: adopting an existing device in our example bot.

andybalaam.uk.to/
#owncast

(Also on Twitch)


One of the coolest tools we use at #1Password has been #opensource ’d!

I present to you Typeshare 2.0! A way to share Rust types across the FFI (supports, Swift, Kotlin, TypeScript, and Go). We use it everyday and I love it, makes things so easy and awesome.

github.com/1Password/typeshare

#rust #swift #kotlin #go #golang #rustlang


Hey folks,

I'm currently looking for new permanent and remote-only opportunities in Europe.

I'm really willing to get my hands dirty with some Rust. My day job is mostly about TypeScript and NodeJS but I have plenty of projects on my GitHub account you can check github.com/yamafaktory .

Boost really appreciated ❤️ !

#rust #rustlang #typescript #nodejs #job


Are you comfortable in C but curious about Rust? Have existing tutorials seemed like they don't apply to the sort of low-level work you do?

Learn Rust the Dangerous Way is my unsafe-first introduction to the Rust language -- starting with code with the same gotchas as C, and introducing idiomatic Rust concepts to improve it. It's a few years old now but you might still find it useful. (I keep meaning to update/extend it but life keeps happening!)

cliffle.com/p/dangerust/

#rust #tutorial


📺 Join me & @bnjbvr_en this afternoon @ 4PM CET for some cozy @matrix #WebAssembly hacking live on stream!
youtube.com/watch?v=hIbBLs1q99…

We are going to be looking at Trinity, Benjamin's supercool side project that lets you write #matrix bots in #rust & WebAssembly. Come for the coolness, stay for the endless hilarity that ensues as I attempt writing Rust code and hope live to tell the story :ablobcateyesflip:
github.com/bnjbvr/trinity


Any Rustaceans looking for a challenge want to implement soft-wrap for Helix Editor?

(Pretty please?) :)

github.com/helix-editor/helix/…

#HelixEditor #rust #dev


It looks to me that this is a case where server built with #rust , like #Mitra ( codeberg.org/silverpill/mitra ) could save a day


scrolling in #deltachat_desktop feels even faster now after switching the backend from cffi to #jsonrpc & #rust

Be ready for #deltachat desktop 1.34, It's coming soon..


That's how much handwritten written code is needed to call a new core function from desktop, before and after jsonrpc. Many thanks to #rust proc macros for making this possible.
#rust


A Memory Safe Implementation of the Network Time Protocol by Folkert de Vries: memorysafety.org/blog/memory-s… #Rust #web
#rust #web


Hey #Rust crate maintainers! I've written a crate metadata validator. Check if your crates need fixes:

lib.rs/dash

#rust


The GNOME ♥ Rust remote hackfest starts tomorrow! Are you planning to join? Learn more or find event organizer contacts here: wiki.gnome.org/Hackfests/Rust2…

#GNOME #Hackfest #Rust


cargo careful: run your Rust code with extra careful debug checking by Ralf Jung: ralfj.de/blog/2022/09/26/cargo… #Rust #language


Do you write code for free and open source projects? Would you like to learn the basics of the Rust programming language? I’m offering to teach the basics of Rust to free and open source software programmers, for free.

liw.fi/training/rust-foss-dev/

#Rust #RustLanguage #FOSS #Training


I dont know if you know but if you know you dont know, now you know. Rustconf videos are up: youtube.com/playlist?list=PL85…

#rust

#rust


Lots of fun happening on matrix-wysiwyg - the world's first(?) native cross-platform WYSIWYG editor, written in #rust (with platform-specific bindings on top) for all your Matrix message composing needs. Here's the test jig for autogenerating test cases (we're still debugging :D)
#rust


You can try and describe Rust syntax but I don’t think you’re going to beat “like trying to read the output of a UART with line noise.”

bunniestudios.com/blog/?p=6375

#rust

#rust


I'm experimenting with the #libreoffice SDK to write a small #nextcloud app. I'm using the #cpp API because I want to wrap it in an #Rust #HTTP backend.

It is hard to figure out how to use the API and questions on Stackoverflow are hard to align with the #libreoffice examples. For example, stackoverflow.com/q/62769483 does not really help. I guess you need to be familiar with the API before you will understand it.

@libreoffice, do you have any pointers to become more comfortable with the API?


#Rust help requested. I am officially at wits end here.

Please take a look at my source file sdlstate.rs.

I'm getting a borrow checker error E0597 on line 39, indicating that tc does not live long enough. However, looking at the sdl2 sources (via its rust-docs), I don't see how my created texture, t, can possibly still refer to tc, which as far as I'm aware, is the only way this error can be generated under current conditions.

error[E0597]: `tc` does not live long enough<br>  --> src/sdlstate.rs:39:21<br>   |<br>14 |   impl<'a> SdlState<'a> {<br>   |        -- lifetime `'a` defined here<br>...<br>39 |           let mut t = tc<br>   |  _____________________^<br>40 | |             .create_texture(<br>41 | |                 Some(sdl2::pixels::PixelFormatEnum::RGBA8888),<br>42 | |                 sdl2::render::TextureAccess::Streaming,<br>43 | |                 self.width,<br>44 | |                 self.height,<br>45 | |             )<br>   | |_____________^ borrowed value does not live long enough<br>...<br>49 |           self.current_texture.set(Some(t));<br>   |           --------------------------------- argument requires that `tc` is borrowed for `'a`<br>...<br>56 |       }<br>   |       - `tc` dropped here while still borrowed<br><br>

Why is this happening? Why can't I re-arrange the code to prevent this from happening?

Right now, the only way this code will compile and run correctly is if I manually inject the re-paint code where I invoke f(), which utterly defeats the purpose and benefit of using closures in the first place.

In an attempt to fix this, I've tried:

  • Replacing the Cell with RefCell.
  • Removing Cell all-together and just using a raw Option type.
  • Removing the 'a lifetime annotation.

None of these work, and almost always introduce some manner of errors on their own.

Please help. Thanks.

#rust


Today I wrote my first GNOME app with rust. It's called switch and I can toggle a 💡 with it 😃

Special thanks to @ebassi for his ongoing series of video streams, which make it much easier for me to get into GNOME and rust programming.

#gnome #gtk #rust


Now that I'm on a new instance, I'll write a new #introduction.

I am a follower of Jesus, mutualist hobbyist programmer, and sysadmin (in that order). I'm passionate about #CooperativeTechnology, #smalltech, and liberating people all around within and without technology.

I'm interested in alternative internet protocols (#Gemini), mobile Linux, real sustainability, and various computer languages (including #Rust and #Zig).

Also hosting benign.town! Join us if you'd like. 🙂


Hello new followers! I've been bad at hashtags, which are crucial here for discoverability, so here's some of them.

I try to toot interesting things related to #activism about #ClimateChange / #ClimateCrisis / #EarthBreakdown, from the perspective of #degrowth / #ClimateJustice / #sustainability. I'm one tiny part of #ExtinctionRebellion.

I build #FOSS / #OpenSource / #commons and #SmallTech using #rust and will write more about that soon.

Third, occasionally #philosophy, #anticapitalism.


Queueing up a new stream: twitch.tv/ebassi

#gnome #gtk #libadwaita #rust


Heads up: phosh-osk-stub moved out of #phosh's repo and to: gitlab.gnome.org/guidog/phosh-… as it acquired more and more cruft while debugging some (now fixed) touch input related issues in #gtk 4.

Mostly mentioning it here since some distros (such as #debian) used it in the past on architectures that had trouble building #rust to fulfill session dependencies (which is not an issue anymore nowadays) so it can safely be dropped.