@mnvr@mastodon.social As far as I remember there's cargo's global setting to have common target directory for the similar reason. The trouble starts when you have any tools relying on presence of target/ and it's content.
Replying to
Remote
Michał Fita
@michalfita@mastodon.social
mastodon 4.8.0-nightly.2026-10-06Embedded software craftsman for over 20 years, fluent in #Bash, #Python & #C++, fan and semiadvocate for #Rust. I deal with Linux very well and everyday.
69 Followers
9 Following
50 Posts
Joined January 14, 2025
Medium:
LinkedIn:
Personal:
Replying to
@peritia@alovely.space Does it? Or just unhappy people have more time to write complaints?
Replying to
@Ambraven@social.mochi.academy Your C++ code uses temporary default as reference; #Rust doesn't have them... unfortunately.
The closest semantically would be IMHO:
fn foo(t: Option<&T>) {
fn inner_foo(t: &T) {
t.toto();
}
inner_foo(t.unwrap_or(&T::default()));
}
Replying to
@soulsource@mastodon.gamedev.place @0xabad1dea@infosec.exchange That happened, they try to scan build.rs for malicious code right now. I think they tried publish crates with dependencies in git as well, and these had malicious code. Especially if you own the domain of that repository it opens huge attack vector.
Replying to
@soph@grrl.me Assuming that's understood. Can we, the humans, draw boundary between violating and meeting the novum IP rules? What use of LLMs as tools would let us pass the test?
Replying to
@Ant8e@fosstodon.org Welcome to the #jobseeker #club on #fediverse.
Remember to use #fedihire tag if you search of job or hire people.
Replying to
@HenrikLievonen It doesn't tell us about symbol names coming from filenames in object files out of rustc. It's actually interesting problem... but I don't have capacity to look into it myself.
Replying to
@katzenmann Assumption idiomatic C++ would crash more than C is (from my experience) wrong (and my delivered fully C++ embedded system to 50k customers).
Then I don't thing on a large project Zig would less likely crash than C as it doesn't have inherent safety enforcement, it's just nicer language to use with some ideas similar to Go.
Replying to
@Harpocrates@infosec.exchange @diegovsky@bolha.us I'm kinda interested, but from different perspective. How to make such protocol stack lightweight enough to fit into embedded system, so their activity at premises cannot be subject to analysis of rouge parties? What you describe is a lot of layers with a lot of code - fine for IM on Android, but less for a device running on 300kB of total RAM.
Replying to
@rogerparkinson Using #Java software to write #Rust doesn't seem right. That's why I ditched #RustRover (actually written in #Kotlin, but still on #JVM), that's superior to #Eclipse.
I used Eclipse #CDT for almost 10 years some time ago, but it became a burden at some point. Then #VSCode appeared... and then #Zed.
I still use last two, as Zed doesn't have any preview extensions due to lack of built in webview support.
Replying to
Replying to
@mattesilver@101010.pl @mortn@mastodon.social There are project in #Rust made in spirit of #Django, just not very mature yet. But, that's #framework only, not functional #CMS.
Continuation of my commentary about role and impact of #LLMs on software engineering.
https://michalfita.medium.com/llms-economy-at-scale-part-2b-00baec37f2a5
Replying to on mastodon.social
@mortn@mastodon.social 🤔 the world probably deserves rewrite of #Drupal in #Rust... maybe not to the letter. But it could use #WebAssembly extensions like #Zed.
For International Children's Day I released `simdsplit` - my #Rust #crate using portable SIMD (#nightly) inspired by @jonhoo@fosstodon.org's https://github.com/jonhoo/brrr video.
What astounds me is the speed up it achieves on Apple M3 silicon when only selected elements are picked and reset in the `Mask`.
The code is ugly and still has bugs. Use at your own risk.
My first hosted on #Codeberg: https://codeberg.org/michalfita/simdsplit
No LLMs used to cook this.
Replying to
Replying to
@katzenmann @_ To build and link with a library, that's not enough. The library can be linked with different options, and pkgconfig was developed to deal with how particular dependency shall be included in the build on particular OS.
There's not Rust's equivalent of pkgconfig at the moment. So your "system" is part of my thinking, but not enough.
Replying to
Replying to
@thejpster@hachyderm.io Ah, OMAP... That SRAM booting doesn't seem far from Cortex-Ms I worked with 🤔 I configured SDRAM controller myself... then actually never loaded any code in there 😉
Replying to
@preslavrachev@mastodon.social Ouch, this snippet is bonkers. Way too complicated to get vector or items from 0 to a.
Why not just Vec::from_iter(0..a)?
Replying to
@r3spawndbae@mastodon.social Thanks for the answer. OK, University level is not the kind of training I could conduct yet.
Replying to
@esther_alter I don't know the answer, haven't been in need for a line count on the page. You can ask on their forum.
Replying to
@ekuber@hachyderm.io This is Catch 22 with where the trade off is going. Correct dependency on system libraries is usually target dependent, often even distro dependent - can maintainer afford the cost of keeping the compatibility? Or can deliver library that works on all? There's certain advantage with cargo as installed packages manager (could be better aligned to that), as it allow to keep tool installed outside the system scope. It's my preferred way, but you have to learn to live with that.
Replying to
@marmarta@chaos.social @kdab@techhub.social are experts of both Qt and Rust, Leon Matthes doesn't seem to be present on Fediverse.
Replying to
@voided Depends, if you're fine with content on the heap, that's relatively simple... with quirks, however.
If you want that on the stack... yeah, thinks are getting complicated. 🤔 Or maybe not... depends.
I'm open to discuss ideas.
Replying to
@paul @Ivovanwilligen if the main service is provided in the EU, LinkedIn may escape that by hosting everything in US.
Replying to
@mxk@hachyderm.io This nice, but it's not feature complete Turbo Vision recreation with movable windows, close button and proper colour theme.
Replying to
@tarajdactyl I think your tag shall be #fedihire not #fedihired... then it's considered a good taste, where more details about the job are actually in the post, including the link to the application.
Replying to
@katzenmann @_ Cargo would need to develop mechanism to deal with OS vendored dependencies at equal level with ones coming from crates.io. That's highly unlikely as this is a hell to bring such feature compatible with Debian, RedHat, Arch, Alpine, *BSD and wherever else packaging system is out there.
Or we need to ditch cargo for releasing for OS ecosystems relying on other build systems and invoking rustc like gcc or clang.
Replying to
@soph@grrl.me But the same interpretation would apply to proprietary code generated using LLMs trained on whatever. If the copyright protection cannot be granted in result of lack of novum IP, that's violation of any license granted to customers in exchange for money. Am I wrong?
If someone would train the model from scratch on own code and materials they have license for (in this case not open-source), that would be their unique tool in their private bag that couldn't be rejected from protection.
Replying to
@bethflint@genomic.social TBH I don't think calling this role "Web Developer" was right decision, if your after #Rust #Web #Frontend #Developer for that role. The difference is significant I think.
Sorry for being picky.
If particular stabilisation PR in #Rust was merged, how to find which release is going to relieve that feature from under nightly restriction?
Replying to
@voided Not sure about event queue, I'd need to better understand what you mean by that, but the thread version should be self-contained. The sleeping thread would be bound to the instance internally, the only issue atm to figure out are lifetime scopes for it. With WeakPtr that's probably easiest to start with.
A month ago a #reputable #security #company sent me #invitation for the initial meeting after I applied for the #job. That was a month after the #application.
I responded with #availability, but haven't heard back till today. I received the same automated message from the same person asking for availability.
I responded.
The email was #bounce with `TLS Negotiation failed, certificate invalid: SSL [Leaf certificate is expired]` 🤦♂️
Is this enough #red-flags?
Replying to
@epage@hachyderm.io @vavakado@mas.to @KFears@mstdn.games Wouldn't be fair to call person the discussion is about to the whiteboard? @dtolnay@rewrite.in.rs seem to be on the fediverse.
Replying to
@r3spawndbae@mastodon.social As you're rare breed paying... may I ask what are you paying for? Or even better, what are you willing to pay for?